Triple
T20147349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldwell 20 |
E491337
|
entity |
| Predicate | separatedFromNearbyObjectBy |
P56200
|
FINISHED |
| Object | dark dust lane |
—
|
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: dark dust lane | Statement: [Caldwell 20, separatedFromNearbyObjectBy, dark dust lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFromNearbyObjectBy Context triple: [Caldwell 20, separatedFromNearbyObjectBy, dark dust lane]
-
A.
distancedFrom
chosen
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
separationFromSpacecraft
Indicates that an object has detached or been released from a spacecraft, ending their physical or operational connection.
-
C.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
D.
separatesNear
Indicates that one entity divides or partitions another entity or space while remaining in close proximity to it.
-
E.
separationBetweenComponents
Indicates a measured distance or gap that exists between two or more components.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679f43bc8190a1cd4768b3e87505 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.