Triple
T24166441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroport T1 station |
E598998
|
entity |
| Predicate | hasTerminusRoleOnLine |
P43881
|
FINISHED |
| Object | L9 Sud |
—
|
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: L9 Sud | Statement: [Aeroport T1 station, hasTerminusRoleOnLine, L9 Sud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusRoleOnLine Context triple: [Aeroport T1 station, hasTerminusRoleOnLine, L9 Sud]
-
A.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
B.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
C.
isOnBranchOfLine
Indicates that something is located on or belongs to a specific branch of a larger line or route.
-
D.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
-
E.
locatedAtTerminusOf
chosen
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.