Triple
T21885044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acamar |
E540383
|
entity |
| Predicate | angularSeparationBetweenComponents |
P69289
|
FINISHED |
| Object | about 8 arcseconds |
—
|
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 8 arcseconds | Statement: [Acamar, angularSeparationBetweenComponents, about 8 arcseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angularSeparationBetweenComponents Context triple: [Acamar, angularSeparationBetweenComponents, about 8 arcseconds]
-
A.
angularSeparationFrom
Indicates the angular distance between two entities as measured from a common observation point.
-
B.
angularSeparationBetweenComplexes
Indicates the angular distance or orientation difference measured between two complexes.
-
C.
separationBetweenComponents
Indicates a measured distance or gap that exists between two or more components.
-
D.
hasCompanionSeparation_arcsec
chosen
Indicates the angular separation, measured in arcseconds, between an object and its companion.
-
E.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.