Triple
T11093713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lendu language |
E262318
|
entity |
| Predicate | isUsedOrallyMoreThanInWriting |
P78839
|
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: [Lendu language, isUsedOrallyMoreThanInWriting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedOrallyMoreThanInWriting Context triple: [Lendu language, isUsedOrallyMoreThanInWriting, true]
-
A.
isPrimarilyOral
chosen
Indicates that the primary mode of expression, communication, or transmission is spoken rather than written or signed.
-
B.
spokenVsWritten
Indicates that the relationship contrasts or distinguishes between spoken and written forms of the same content or expression.
-
C.
requiresOralInterpretation
Indicates that one entity needs spoken language interpretation services to understand or communicate information from another entity.
-
D.
hasOralDiscFunction
Indicates that an entity possesses a specific functional role or capability associated with its oral disc.
-
E.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ed12d88190a4ad8c346d68f11f |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.