Triple
T26187647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niam Khasi |
E654873
|
entity |
| Predicate | linkedToSocialStructure |
P143147
|
FINISHED |
| Object | Khasi clan system |
—
|
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: Khasi clan system | Statement: [Niam Khasi, linkedToSocialStructure, Khasi clan system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToSocialStructure Context triple: [Niam Khasi, linkedToSocialStructure, Khasi clan system]
-
A.
hasSocialStructure
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
C.
linksFriendshipTo
Indicates a relationship that connects an entity to another entity with which it has a friendship.
-
D.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
E.
associatesStructure
chosen
Indicates a relationship where one entity is linked or connected to a particular structure, typically to denote that the structure is relevant, attached, or functionally associated with it.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 8:43 p.m.