Triple
T37108171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Corporation |
E918906
|
entity |
| Predicate | mayOwn |
P38332
|
FINISHED |
| Object | power plants |
—
|
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: power plants | Statement: [Energy Corporation, mayOwn, power plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOwn Context triple: [Energy Corporation, mayOwn, power plants]
-
A.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
B.
canOwn
chosen
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
-
C.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
D.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
E.
mayRuleOver
Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.