Triple
T23748950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Auber |
E586903
|
entity |
| Predicate | hasNearbyMetroLines |
P33788
|
FINISHED |
| Object | Paris Métro line 3 |
—
|
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: Paris Métro line 3 | Statement: [Rue Auber, hasNearbyMetroLines, Paris Métro line 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMetroLines Context triple: [Rue Auber, hasNearbyMetroLines, Paris Métro line 3]
-
A.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
-
B.
hasMetroLine
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
C.
nearUndergroundLine
chosen
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
D.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
-
E.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc118dc8190b0b92e402b9a7dd4 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.