Triple
T30551399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mairie d’Issy |
E777568
|
entity |
| Predicate | positionOnLine12 |
P38325
|
FINISHED |
| Object | southwestern terminus |
—
|
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: southwestern terminus | Statement: [Mairie d’Issy, positionOnLine12, southwestern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLine12 Context triple: [Mairie d’Issy, positionOnLine12, southwestern terminus]
-
A.
positionOnLine
chosen
Indicates that one entity occupies a specific location along a defined line or linear path in relation to another.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionInProductLine
Indicates the specific place or order an item occupies within a defined product line or series.
-
D.
positionOnNumbers
Indicates a relationship where one entity occupies a specific numerical position or rank relative to others in an ordered sequence of numbers.
-
E.
linePositioning
Indicates the relative arrangement or alignment of elements along a line or linear sequence.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 29, 2026, 8:20 p.m.