Triple
T24345100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MI 2N "Eole" |
E613617
|
entity |
| Predicate | introducedForLine |
P3018
|
FINISHED |
| Object | RER E |
—
|
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: RER E | Statement: [MI 2N "Eole", introducedForLine, RER E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForLine Context triple: [MI 2N "Eole", introducedForLine, RER E]
-
A.
accessibleForLine
Indicates that something (such as a resource, area, or facility) can be reached, used, or served by a particular line (e.g., a transport or service line).
-
B.
introducedFor
chosen
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
C.
introducedByProductLine
Indicates that one product line is responsible for introducing, launching, or bringing another product, feature, or offering into the market or portfolio.
-
D.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
E.
lineNumberingIntroduced
Indicates that a system, document, or text has had line numbering initiated or enabled.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29328b0288190a580939e8863b0c2 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.