Triple
T3886037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 944 Hidalgo |
E92942
|
entity |
| Predicate | wasFirstOfType |
P46310
|
FINISHED |
| Object | one of the first known centaurs |
—
|
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: one of the first known centaurs | Statement: [944 Hidalgo, wasFirstOfType, one of the first known centaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstOfType Context triple: [944 Hidalgo, wasFirstOfType, one of the first known centaurs]
-
A.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
B.
isFirstInCategory
chosen
Indicates that an entity is the earliest or primary member within a defined category or group.
-
C.
firstOf
Indicates that one entity is the earliest or initial member in an ordered sequence or collection relative to the others.
-
D.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
E.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec942bfc8190a398fe370715a28b |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.