Triple
T30551408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mairie d’Issy |
E777568
|
entity |
| Predicate | lineRenamedTo |
P3432
|
FINISHED |
| Object | Paris Métro Line 12 |
—
|
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 12 | Statement: [Mairie d’Issy, lineRenamedTo, Paris Métro Line 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineRenamedTo Context triple: [Mairie d’Issy, lineRenamedTo, Paris Métro Line 12]
-
A.
renamedTo
chosen
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
B.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
C.
renamedAlongWith
Indicates that an entity was renamed at the same time and in coordination with another entity’s renaming.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:20 p.m.