Triple
T525238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles de Gaulle–Étoile metro station |
E10901
|
entity |
| Predicate | isMajorInterchange |
P14730
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Charles de Gaulle–Étoile metro station, isMajorInterchange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorInterchange Context triple: [Charles de Gaulle–Étoile metro station, isMajorInterchange, true]
-
A.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
B.
isMajor
chosen
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
C.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
E.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b7f448819087e5e7f3b37d7142 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.