Triple
T37317502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoche metro station |
E926375
|
entity |
| Predicate | locatedOutsideCityLimitsOf |
P22652
|
FINISHED |
| Object | Paris |
E568
|
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: Paris | Statement: [Hoche metro station, locatedOutsideCityLimitsOf, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOutsideCityLimitsOf Context triple: [Hoche metro station, locatedOutsideCityLimitsOf, Paris]
-
A.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
B.
locatedOutsideJurisdiction
Indicates that one entity is situated beyond the legal or administrative authority area of another entity or governing body.
-
C.
crossesCityLimit
Indicates that an entity moves from outside to inside, or inside to outside, the defined boundary of a city.
-
D.
isOutsideFarmSystemOf
Indicates that one entity is not part of, or not governed by, the agricultural or farm management system associated with another entity.
-
E.
liesOutside
chosen
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
- F. None of above.
Provenance (4 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4082398d68819089a22b4a84109899 |
completed | June 28, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.