Triple
T37108153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Corporation |
E918906
|
entity |
| Predicate | mayHaveLegalForm |
P96805
|
FINISHED |
| Object | corporation |
—
|
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: corporation | Statement: [Energy Corporation, mayHaveLegalForm, corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveLegalForm Context triple: [Energy Corporation, mayHaveLegalForm, corporation]
-
A.
proposedLegalForm
Indicates the legal structure or organizational form that has been suggested or planned for an entity, but not yet finalized or adopted.
-
B.
hasLegalStructure
chosen
Indicates that an entity possesses a specific formal legal organization or classification under law.
-
C.
typicalLegalForm
Indicates the standard or commonly used legal organizational form associated with an entity.
-
D.
belongsToCompanyLegalForm
Indicates that an entity is associated with or classified under a specific legal form of a company.
-
E.
countryLegalForm
Indicates the legal or organizational form that an entity has under the laws of a specific country.
- 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.