Triple
T5237672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tablelands |
E118262
|
entity |
| Predicate | canCover |
P52868
|
FINISHED |
| Object | extensive areas |
—
|
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: extensive areas | Statement: [tablelands, canCover, extensive areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCover Context triple: [tablelands, canCover, extensive areas]
-
A.
mayCover
chosen
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
B.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
C.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b27990c8190b6a3c24de09c8c18 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.