Triple
T25094492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakar tribe |
E628550
|
entity |
| Predicate | hasNotableCentre |
P6682
|
FINISHED |
| Object | Quetta |
—
|
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: Quetta | Statement: [Kakar tribe, hasNotableCentre, Quetta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCentre Context triple: [Kakar tribe, hasNotableCentre, Quetta]
-
A.
hasNotableCenter
chosen
Indicates that an entity possesses a significant or distinguished central location, facility, or hub associated with it.
-
B.
notableCenter
Indicates that an entity is recognized as an important or prominent central point, hub, or focal location for another entity or activity.
-
C.
hasCentralLandmark
Indicates that a place or area contains a primary or defining landmark located at or near its center.
-
D.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
E.
hasNotableTown
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 18, 2026, 6:24 a.m.