Triple
T10510385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kambojas |
E247895
|
entity |
| Predicate | possibleLanguage |
P94296
|
FINISHED |
| Object | Iranian 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: Iranian language | Statement: [Kambojas, possibleLanguage, Iranian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleLanguage Context triple: [Kambojas, possibleLanguage, Iranian language]
-
A.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
B.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
C.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
- F. None of above. chosen
Provenance (4 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b542088190868531f84deaf9e4 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:27 p.m.