Triple
T5860375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiron |
E130259
|
entity |
| Predicate | afterDeathHonoredAs |
P58157
|
FINISHED |
| Object | constellationCentaurus |
—
|
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: constellationCentaurus | Statement: [Chiron, afterDeathHonoredAs, constellationCentaurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDeathHonoredAs Context triple: [Chiron, afterDeathHonoredAs, constellationCentaurus]
-
A.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
B.
alsoHonoredAs
chosen
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
C.
hasHonoureePlaceOfDeath
Indicates the place where the honoured person died.
-
D.
posthumousReputation
Indicates the reputation or standing attributed to a person after their death.
-
E.
hasPartInHisHonor
Indicates that something includes or contains a part, section, or component that is dedicated or named in honor of a particular person.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.