Triple
T3728426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qashqai |
E79003
|
entity |
| Predicate | hasSpeakerCommunityType |
P3292
|
FINISHED |
| Object | tribal confederation |
—
|
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: tribal confederation | Statement: [Qashqai, hasSpeakerCommunityType, tribal confederation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakerCommunityType Context triple: [Qashqai, hasSpeakerCommunityType, tribal confederation]
-
A.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
-
B.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
haveSpeakerPopulation
Indicates that an entity has a specified number or population size of people who speak a particular language.
-
E.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf921bc81908bb347d6b9204670 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.