Triple
T15554267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London |
E370827
|
entity |
| Predicate | replacedMechanism |
P29646
|
FINISHED |
| Object | first-price gas auction |
—
|
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: first-price gas auction | Statement: [London, replacedMechanism, first-price gas auction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedMechanism Context triple: [London, replacedMechanism, first-price gas auction]
-
A.
replacedOrComplementedMechanism
Indicates that one mechanism has been superseded by, or now functions alongside as a complement to, another mechanism.
-
B.
upgradeMechanism
Indicates a relationship where one entity serves as the method, process, or system by which another entity is improved, updated, or enhanced.
-
C.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
D.
reconciliationMechanism
Indicates a process or method through which conflicting parties restore harmony, resolve differences, or repair their relationship.
-
E.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a96c0c88190808f68601a36b506 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.