Triple
T4657730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drum Point Lighthouse |
E102448
|
entity |
| Predicate | laterPowerSource |
P8164
|
FINISHED |
| Object | electricity |
—
|
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: electricity | Statement: [Drum Point Lighthouse, laterPowerSource, electricity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPowerSource Context triple: [Drum Point Lighthouse, laterPowerSource, electricity]
-
A.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
B.
batterySupplier
Indicates that one entity serves as the supplier or provider of batteries to another entity.
-
C.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
D.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
E.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd631a855c81909773737fd238a14d |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.