Triple
T30896742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghilzai tribe |
E787040
|
entity |
| Predicate | notableSubtribe |
P104422
|
FINISHED |
| Object | Hotak |
E311855
|
NE 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: Hotak | Statement: [Ghilzai tribe, notableSubtribe, Hotak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSubtribe Context triple: [Ghilzai tribe, notableSubtribe, Hotak]
-
A.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
hasNotableSubtribe
chosen
Indicates that an entity (typically a larger tribal or ethnic group) includes a particular subtribe that is especially recognized or notable.
-
C.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
D.
notableSubculture
Indicates that one entity is a significant or well-recognized subculture within the context or domain of the other entity.
-
E.
notableDescendantTribe
Indicates that a tribe has a particularly important or historically significant descendant tribe associated with it.
- F. None of above.
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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7ebcfbc81909f2ba04b578d7a6c |
completed | June 10, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:49 p.m.