Triple
T27546361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBT |
E695372
|
entity |
| Predicate | usesElamEnding |
P83941
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TBT, usesElamEnding, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElamEnding Context triple: [TBT, usesElamEnding, true]
-
A.
ElamEnding
chosen
Indicates that an entity marks the end or termination of something related to Elam (e.g., an Elam-related period, event, or process).
-
B.
usesFinalConsonants
Indicates that an entity employs or contains consonant sounds in final position, such as at the end of a word, syllable, or phonological unit.
-
C.
hasEndingTone
Indicates that something concludes with a particular tone, mood, or intonational quality.
-
D.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
E.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:33 p.m.