Triple
T37452296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypsilophodontidae |
E930700
|
entity |
| Predicate | traditionalGrouping |
P62073
|
FINISHED |
| Object | ornithopod dinosaurs |
—
|
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: ornithopod dinosaurs | Statement: [Hypsilophodontidae, traditionalGrouping, ornithopod dinosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalGrouping Context triple: [Hypsilophodontidae, traditionalGrouping, ornithopod dinosaurs]
-
A.
typicalGroup
chosen
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
B.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
-
C.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
D.
groupingType
Indicates how multiple entities are categorized or clustered together based on a shared grouping criterion.
-
E.
traditionalStructure
Indicates that something follows or embodies a customary, historically established form, pattern, or organizational framework.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:17 p.m.