Triple
T7960624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Mineral Leasing Act of 1938 |
E184853
|
entity |
| Predicate | typeOfResourceCovered |
P68335
|
FINISHED |
| Object | oil |
—
|
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: oil | Statement: [Indian Mineral Leasing Act of 1938, typeOfResourceCovered, oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfResourceCovered Context triple: [Indian Mineral Leasing Act of 1938, typeOfResourceCovered, oil]
-
A.
typeOfResourceStudied
Indicates that a particular resource is the subject or focus of study or analysis in a given context.
-
B.
typeOfResourceRegulated
chosen
Indicates that one entity specifies the kind or category of resource that is subject to regulation by another entity.
-
C.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
D.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
E.
hasTypeOfResource
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b8136448190890f007fb4fb7625 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:12 p.m.