Triple
T3402551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomé |
E71688
|
entity |
| Predicate | electricityFrequency |
P15377
|
FINISHED |
| Object | 50 Hz |
—
|
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: 50 Hz | Statement: [Lomé, electricityFrequency, 50 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricityFrequency Context triple: [Lomé, electricityFrequency, 50 Hz]
-
A.
usesElectricFrequency
chosen
Indicates that one entity operates or functions by relying on a specified electric frequency provided by another entity or context.
-
B.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
C.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
D.
usesElectricityStandard
Indicates that one entity operates according to, or is compatible with, the electricity supply standard defined or used by another entity.
-
E.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8e78ec8819089417666dc29f412 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.