Triple
T30741134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ether |
E782691
|
entity |
| Predicate | sourceTextFor |
P131980
|
FINISHED |
| Object | Book of Ether |
—
|
NE NERFINISHED |
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: Book of Ether | Statement: [Ether, sourceTextFor, Book of Ether]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTextFor Context triple: [Ether, sourceTextFor, Book of Ether]
-
A.
typicalSourceText
Indicates that the related entity is a common or representative textual source from which information, examples, or data about another entity are typically drawn.
-
B.
textSources
chosen
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
C.
sourceRockFor
Indicates that one geological formation serves as the originating rock from which another material, such as hydrocarbons or minerals, is generated or derived.
-
D.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
E.
textEditorsOfSource
Indicates that the related entities are text editors used to create or modify the given source.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 8:38 p.m.