Triple
T8606386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonaparte Basin |
E203807
|
entity |
| Predicate | containsSealRocks |
P1326
|
FINISHED |
| Object | shale |
—
|
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: shale | Statement: [Bonaparte Basin, containsSealRocks, shale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSealRocks Context triple: [Bonaparte Basin, containsSealRocks, shale]
-
A.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
hasRegionalStone
Indicates that something possesses or is associated with a characteristic stone specific to a particular region.
-
C.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
D.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
E.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on 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.