Triple
T20665773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antlia 2 Dwarf Galaxy |
E507881
|
entity |
| Predicate | angularPosition |
P140976
|
FINISHED |
| Object | constellation Antlia |
—
|
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: constellation Antlia | Statement: [Antlia 2 Dwarf Galaxy, angularPosition, constellation Antlia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularPosition Context triple: [Antlia 2 Dwarf Galaxy, angularPosition, constellation Antlia]
-
A.
positionStyle
Indicates how an entity is positioned or arranged relative to a reference frame, layout, or context.
-
B.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
C.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
D.
ribbonPosition
Indicates the spatial or ordered placement of a ribbon relative to a reference object or coordinate system.
-
E.
stylePositioning
Indicates how an entity is spatially or visually arranged or aligned relative to a reference frame or other elements.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c2c6d48190bbfe505cf7d973f9 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.