Triple
T31812325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marco Polo Tower |
E812039
|
entity |
| Predicate | hasEnergyConcept |
P188106
|
FINISHED |
| Object | high energy-efficiency standards |
—
|
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: high energy-efficiency standards | Statement: [Marco Polo Tower, hasEnergyConcept, high energy-efficiency standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyConcept Context triple: [Marco Polo Tower, hasEnergyConcept, high energy-efficiency standards]
-
A.
hasEnergyRole
Indicates that one entity plays a specific functional role in the production, distribution, management, or use of energy in relation to another entity.
-
B.
hasEnergyResource
Indicates that an entity possesses, controls, or is associated with a source of usable energy.
-
C.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
D.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
E.
energyBase
Indicates that one entity serves as the fundamental source or basis of energy for another entity or process.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 30, 2026, 11:44 p.m.