Triple
T34433827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lacq industrial platform |
E883897
|
entity |
| Predicate | primaryResourceProcessed |
P60481
|
FINISHED |
| Object | natural gas |
—
|
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: natural gas | Statement: [Lacq industrial platform, primaryResourceProcessed, natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResourceProcessed Context triple: [Lacq industrial platform, primaryResourceProcessed, natural gas]
-
A.
primaryProcess
Indicates that one process is the main or most fundamental process in relation to another process or within a given system or context.
-
B.
primaryResourceType
chosen
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
C.
originProcess
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
-
D.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
E.
processedFor
Indicates that something has been handled, treated, or transformed specifically for the benefit, use, or purpose of 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.