Triple
T32133788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khas Arya |
E820717
|
entity |
| Predicate | historicalIdentity |
P67010
|
FINISHED |
| Object | Khas people |
—
|
NE NERFINISHED |
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: Khas people | Statement: [Khas Arya, historicalIdentity, Khas people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalIdentity Context triple: [Khas Arya, historicalIdentity, Khas people]
-
A.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
B.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
C.
historicalEntityType
Indicates that an entity belongs to a specific historical category or classification, such as a type, role, or function recognized in a historical context.
-
D.
historicalIdentificationOf
chosen
Indicates that one entity has been identified, classified, or recognized as another entity within a historical context or by historical sources.
-
E.
historicalRepresentative
Indicates that one entity serves or served as an official representative or delegate of another entity in a historical 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: May 1, 2026, 12:30 a.m.