Triple
T22174947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isti |
E548024
|
entity |
| Predicate | usedPrimarilyInSpokenContext |
P10000
|
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: [Isti, usedPrimarilyInSpokenContext, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPrimarilyInSpokenContext Context triple: [Isti, usedPrimarilyInSpokenContext, true]
-
A.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
-
B.
usedPrimarilyIn
chosen
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
C.
spokenPrimarilyOn
Indicates that something (typically a language or dialect) is used mainly for spoken communication in a particular context, region, or group.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
isSpokenAround
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6b755c81909e9bd2a588c065b3 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.