Triple
T10618205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharia |
E295177
|
entity |
| Predicate | hasEvidentialityFeatures |
P50347
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Kharia, hasEvidentialityFeatures, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvidentialityFeatures Context triple: [Kharia, hasEvidentialityFeatures, limited]
-
A.
hasEvidentials
chosen
Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
-
B.
hasLinguisticFeature
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
C.
hasLanguageEvidenceOf
Indicates that there is linguistic or textual evidence supporting, documenting, or attesting to the related entity or claim.
-
D.
hasVerbalFeature
Indicates that an entity possesses a specific verbal property, characteristic, or behavior related to speech or language.
-
E.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
- 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.