Triple
T35690786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentes system |
E1031283
|
entity |
| Predicate | astrographicalRegion |
P9990
|
FINISHED |
| Object | Outer Rim Territories |
—
|
NE NERFINISHED |
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: Outer Rim Territories | Statement: [Gentes system, astrographicalRegion, Outer Rim Territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astrographicalRegion Context triple: [Gentes system, astrographicalRegion, Outer Rim Territories]
-
A.
solarSystemRegion
Indicates that one entity is a region or area located within the solar system that is associated with or contains the other entity.
-
B.
locatedInSkyRegion
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
C.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
D.
radiantStarRegion
Indicates a region in space that is prominently illuminated or dominated by the radiance of a particular star.
-
E.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.