Triple
T37435263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 6 (Paris Métro) |
E930245
|
entity |
| Predicate | hasRenumberingDate |
—
|
GENERATED |
| Object | 1909 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRenumberingDate Context triple: [Line 6 (Paris Métro), hasRenumberingDate, 1909]
-
A.
canBeRenumberedTo
Indicates that one entity’s identifiers or numbering scheme can be systematically changed to match or correspond to another set of identifiers or numbering.
-
B.
canBeRenumberedFrom
Indicates that one entity’s numbering or identifier sequence is allowed to be changed starting from the numbering or identifier of another entity.
-
C.
hasRebuiltDate
Indicates the date on which something was rebuilt or reconstructed.
-
D.
mayBeRenumbered
Indicates that an entity’s identifier or numbering is allowed to change under certain conditions.
-
E.
renumbered
Indicates that an entity’s identifying number or sequence position has been changed to a new numbering scheme.
- F. None of above. chosen
Provenance (1 batch)
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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.