Triple
T4943422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMC |
E110989
|
entity |
| Predicate | distanceAnchorFor |
P37167
|
FINISHED |
| Object | extragalactic distance scale |
—
|
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: extragalactic distance scale | Statement: [LMC, distanceAnchorFor, extragalactic distance scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceAnchorFor Context triple: [LMC, distanceAnchorFor, extragalactic distance scale]
-
A.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
B.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
C.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
-
D.
isAnchorOf
chosen
Indicates that one entity serves as a fixed reference or stabilizing point for another entity, to which the latter is attached or by which it is held in place.
-
E.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a7650c8190b046b65072fd8eae |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.