Triple
T3653604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reptilia |
E77476
|
entity |
| Predicate | historicalGroup |
P9609
|
FINISHED |
| Object | sauropsids |
—
|
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: sauropsids | Statement: [Reptilia, historicalGroup, sauropsids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalGroup Context triple: [Reptilia, historicalGroup, sauropsids]
-
A.
historicalProvinceGroup
Indicates that two or more provinces are grouped together based on sharing a common historical administrative or territorial affiliation.
-
B.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
C.
historicalPass
Indicates that an entity has successfully completed or passed a historical event, period, or examination related to history.
-
D.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b805a48190a7bc230a382365d6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.