Triple
T17070428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Agnettes |
E414201
|
entity |
| Predicate | isOnBranchOfLine |
P125739
|
FINISHED |
| Object | northwestern branch of Line 13 |
—
|
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: northwestern branch of Line 13 | Statement: [Les Agnettes, isOnBranchOfLine, northwestern branch of Line 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnBranchOfLine Context triple: [Les Agnettes, isOnBranchOfLine, northwestern branch of Line 13]
-
A.
isJunctionOnLine
Indicates that a particular junction lies on, or is part of, a specified line.
-
B.
isOnBranch
Indicates that one entity is physically positioned atop or supported by a branch of another entity.
-
C.
isBetweenStationsOnLine
Indicates that something is located or occurs between two stations along the same transit line.
-
D.
isMajorJunctionOnLine
Indicates that a location serves as a primary connecting junction along a particular line or route.
-
E.
isOnShortLine
Indicates that one entity is positioned on or along a line segment that is classified as short relative to other lines in the context.
- F. None of above. chosen
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc0982c8190916f9905ddb5e575 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.