Triple
T26331693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | phlogiston theory |
E662402
|
entity |
| Predicate | explained |
P3638
|
FINISHED |
| Object | burning of charcoal |
—
|
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: burning of charcoal | Statement: [phlogiston theory, explained, burning of charcoal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explained Context triple: [phlogiston theory, explained, burning of charcoal]
-
A.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
laterExplained
Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
-
C.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
D.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
E.
betterUnderstoodAs
Indicates that one concept, term, or representation is more accurately or clearly interpreted when viewed as another specified concept, term, or representation.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f69fd248190bb747dde86643732 |
completed | May 2, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:34 p.m.