Triple
T38600404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benton Group |
E934194
|
entity |
| Predicate | potentialResource |
P20795
|
FINISHED |
| Object | hydrocarbon source rock |
—
|
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: hydrocarbon source rock | Statement: [Benton Group, potentialResource, hydrocarbon source rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialResource Context triple: [Benton Group, potentialResource, hydrocarbon source rock]
-
A.
coveredResource
Indicates that one entity serves as a resource that is included within the scope or protection of another entity (such as a policy, agreement, or coverage).
-
B.
hasResourcePotential
chosen
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
C.
secondaryResource
Indicates that a resource serves as a secondary, supporting, or auxiliary resource in relation to a primary one.
-
D.
potentialUse
Indicates that one entity could be used for, or is suitable for, a particular function, purpose, or application involving another entity.
-
E.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.