Triple
T26259220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus Galaxy |
E656800
|
entity |
| Predicate | locatedInFictionRelativeTo |
P47231
|
FINISHED |
| Object | far from the Milky Way galaxy |
—
|
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: far from the Milky Way galaxy | Statement: [Pegasus Galaxy, locatedInFictionRelativeTo, far from the Milky Way galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFictionRelativeTo Context triple: [Pegasus Galaxy, locatedInFictionRelativeTo, far from the Milky Way galaxy]
-
A.
locationWithinFiction
Indicates that one fictional location is situated inside or contained within another fictional location.
-
B.
locatedNearFiction
chosen
Indicates that one fictional entity or place is situated close to another within an imagined or narrative context.
-
C.
locatedInFictionalEvent
Indicates that one entity (typically a place, object, or character) exists or occurs within the context or setting of a fictional event.
-
D.
positionInFiction
Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
-
E.
locatedInFictionalContext
Indicates that one entity exists or occurs within the setting or universe of a fictional work associated with another entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 26, 2026, 9:09 p.m.