Triple
T8606677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timor Sea Treaty |
E203814
|
entity |
| Predicate | resourceTypeCovered |
P38809
|
FINISHED |
| Object | petroleum |
—
|
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: petroleum | Statement: [Timor Sea Treaty, resourceTypeCovered, petroleum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceTypeCovered Context triple: [Timor Sea Treaty, resourceTypeCovered, petroleum]
-
A.
serviceCovered
Indicates that a particular service is included within the scope, benefits, or obligations defined by a given plan, agreement, or coverage.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
D.
typeOfCoverage
chosen
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
E.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46eabe2c8190a2d13c353055a785 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.