Triple
T10618223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharia |
E295177
|
entity |
| Predicate | subjectToLanguageDocumentation |
P43659
|
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: [Kharia, subjectToLanguageDocumentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToLanguageDocumentation Context triple: [Kharia, subjectToLanguageDocumentation, true]
-
A.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
-
B.
hasLinguisticDocumentation
chosen
Indicates that there exists recorded linguistic information or documentation about the language or linguistic properties of the subject.
-
C.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
-
D.
languageFamilyDocumented
Indicates that there exists documentation or records describing the language family to which the entity’s language belongs.
-
E.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d6df6ee1848190a7d5fcd40b06cfe3 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:19 p.m.