Triple
T35690828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orto Plutonia system |
E1031285
|
entity |
| Predicate | sectorCapitalNearby |
P183826
|
FINISHED |
| Object | Anoat |
E1031288
|
NE 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: Anoat | Statement: [Orto Plutonia system, sectorCapitalNearby, Anoat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorCapitalNearby Context triple: [Orto Plutonia system, sectorCapitalNearby, Anoat]
-
A.
nearbyEconomicActivity
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
-
B.
hasMajorCompanyNearby
Indicates that a location or entity is situated close to at least one large or significant company.
-
C.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
D.
hasNearbyEconomicRegion
Indicates that one economic region is geographically close to or adjacent to another economic region.
-
E.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
- F. None of above. chosen
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38729104048190b20cdefbebc27fe0 |
completed | June 21, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.