Triple
T7802260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saurischia |
E180458
|
entity |
| Predicate | majorSubgroupOf |
P53577
|
FINISHED |
| Object | saurischian 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: saurischian dinosaurs | Statement: [Saurischia, majorSubgroupOf, saurischian dinosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSubgroupOf Context triple: [Saurischia, majorSubgroupOf, saurischian dinosaurs]
-
A.
subgroupCategory
chosen
Indicates that one category functions as a more specific subgroup within the scope of another, broader category.
-
B.
majorGroup
Indicates that an entity belongs to or is classified under a primary or overarching group within a broader categorization.
-
C.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
D.
linguisticSubgroup
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
E.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.