Triple
T17886896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hourman |
E447221
|
entity |
| Predicate | powerDuration |
P129157
|
FINISHED |
| Object | one hour |
—
|
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: one hour | Statement: [Hourman, powerDuration, one hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerDuration Context triple: [Hourman, powerDuration, one hour]
-
A.
periodInPowerEnd
Indicates the point in time when an entity’s tenure or period in power comes to an end.
-
B.
powerStatus
Indicates whether an entity is currently powered on, off, or in another defined power state.
-
C.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
D.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
-
E.
powerCharacteristic
Indicates a relationship where one entity has a specific power-related property, capacity, or performance attribute characterized by the other entity.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c13bd288190a0302010ba4d0532 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.