Triple
T17242969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indochinese tiger |
E418547
|
entity |
| Predicate | relativeBodySize |
P8238
|
FINISHED |
| Object | smaller than Bengal tiger |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: smaller than Bengal tiger | Statement: [Indochinese tiger, relativeBodySize, smaller than Bengal tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeBodySize Context triple: [Indochinese tiger, relativeBodySize, smaller than Bengal tiger]
-
A.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
B.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
C.
memberOfBodySize
Indicates that one entity is a component or part whose size contributes to or characterizes the overall body size of another entity.
-
D.
relativeSizeWithinSite
Indicates the comparative size relationship of one entity to another within the same site or local context.
-
E.
hasRelativeSize
chosen
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e21003c81908c884a3c8712676a |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.