Triple
T24581773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boone Formation |
E608268
|
entity |
| Predicate | hasChertContent |
P156430
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Boone Formation, hasChertContent, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChertContent Context triple: [Boone Formation, hasChertContent, high]
-
A.
hasTarContent
Indicates that something contains or is characterized by a certain amount or presence of tar.
-
B.
hasContentFrom
Indicates that one entity’s content is derived from, includes, or is based on another entity.
-
C.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
D.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
E.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
- F. None of above. chosen
Provenance (4 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:29 a.m.