Triple
T22355586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achernar |
E552642
|
entity |
| Predicate | hasCompanionSeparation |
P147890
|
FINISHED |
| Object | about 12 AU |
—
|
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: about 12 AU | Statement: [Achernar, hasCompanionSeparation, about 12 AU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionSeparation Context triple: [Achernar, hasCompanionSeparation, about 12 AU]
-
A.
hasCompanionSeparation_arcsec
Indicates the angular separation, measured in arcseconds, between an object and its companion.
-
B.
hasCompanionDeparture
Indicates that an entity’s departure is associated with, or accompanied by, the departure of a companion entity.
-
C.
separatedAlongWith
Indicates that an entity becomes separated from something while simultaneously being accompanied or grouped with another specified entity during the separation.
-
D.
hasCompanionCase
Indicates that an entity is associated with another related case that accompanies or parallels it.
-
E.
laterSeparatedFrom
Indicates that one entity became separated from another at a later time than some referenced separation event.
- F. None of above. chosen
Provenance (4 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157cf94508190b0f2c63ddfecb813 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.