Triple
T30570418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Quadrant |
E778107
|
entity |
| Predicate | coordinateDesignation |
P140826
|
FINISHED |
| Object | one of four galactic quadrants |
—
|
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: one of four galactic quadrants | Statement: [Delta Quadrant, coordinateDesignation, one of four galactic quadrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateDesignation Context triple: [Delta Quadrant, coordinateDesignation, one of four galactic quadrants]
-
A.
clusterDesignation
Indicates that an entity is assigned to or identified as part of a specific cluster or grouping.
-
B.
coordinateName
chosen
Indicates that an entity has a specific coordinate-based name or label used to identify its position.
-
C.
mountDesignation
Indicates that one entity is designated or assigned as the mount (e.g., riding or support animal/vehicle) for another entity.
-
D.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
E.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:22 p.m.