Triple
T31103048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddock 11 |
E792724
|
entity |
| Predicate | designedToContain |
P154879
|
FINISHED |
| Object | Indominus rex |
—
|
NE NERFINISHED |
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: Indominus rex | Statement: [Paddock 11, designedToContain, Indominus rex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToContain Context triple: [Paddock 11, designedToContain, Indominus rex]
-
A.
designedToAccommodate
chosen
Indicates that something has been intentionally created or configured in a way that can suitably hold, support, or serve a particular thing, group, or purpose.
-
B.
plannedToContain
Indicates that one entity was intended or designed to include, hold, or encompass another entity as part of a prior plan or arrangement.
-
C.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
D.
believedToContain
Indicates that something is thought or assumed to hold, include, or possess something else, without certainty.
-
E.
containmentStructure
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 9:03 p.m.