Triple
T34982195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidiian language |
E1008843
|
entity |
| Predicate | spokenByCharacterGroup |
P173914
|
FINISHED |
| Object | Vidiian doctors |
—
|
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: Vidiian doctors | Statement: [Vidiian language, spokenByCharacterGroup, Vidiian doctors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByCharacterGroup Context triple: [Vidiian language, spokenByCharacterGroup, Vidiian doctors]
-
A.
spokenByCharacterClass
chosen
Indicates that an utterance or line of dialogue is produced by a character belonging to a specified character class or type.
-
B.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
C.
spokenToCharacter
Indicates that one character has verbally addressed or communicated directly with another character.
-
D.
spokenOfAs
Indicates that one entity is referred to, characterized, or talked about in a particular way by another entity or within a given context.
-
E.
spokenByEthnicGroup
Indicates that a particular language, dialect, or speech variety is used or spoken by a specified ethnic group.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.