Triple
T21658019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LUMA Energy |
E534516
|
entity |
| Predicate | contractNature |
P405
|
FINISHED |
| Object | public-private partnership |
—
|
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: public-private partnership | Statement: [LUMA Energy, contractNature, public-private partnership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractNature Context triple: [LUMA Energy, contractNature, public-private partnership]
-
A.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
C.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
D.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
E.
legalNatureOfInstrument
Indicates the type or legal character of an instrument (such as whether it is a contract, deed, will, etc.) within a legal framework.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c05a8d881909f747635bdb4ef09 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.