Triple
T24921506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tegbo |
E618737
|
entity |
| Predicate | hasSpokenOrWrittenForm |
P15075
|
FINISHED |
| Object | primarily spoken language |
—
|
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: primarily spoken language | Statement: [Tegbo, hasSpokenOrWrittenForm, primarily spoken language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenOrWrittenForm Context triple: [Tegbo, hasSpokenOrWrittenForm, primarily spoken language]
-
A.
hasWrittenForm
Indicates that an entity is associated with a specific written or textual representation.
-
B.
hasSpokenFormOnly
Indicates that the entity exists or is recognized only in spoken form and has no corresponding written representation.
-
C.
spokenVsWritten
Indicates that the relationship contrasts or distinguishes between spoken and written forms of the same content or expression.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
usedInSpokenForm
chosen
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 18, 2026, 5:28 a.m.