Triple
T15277010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kilba people |
E365166
|
entity |
| Predicate | traditionalDefense |
P108546
|
FINISHED |
| Object | fortified hilltop villages |
—
|
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: fortified hilltop villages | Statement: [Kilba people, traditionalDefense, fortified hilltop villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDefense Context triple: [Kilba people, traditionalDefense, fortified hilltop villages]
-
A.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
B.
traditionalShield
Indicates that an entity functions as or possesses a shield that is made or used according to traditional or culturally established practices.
-
C.
defenseIncludes
chosen
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
D.
traditionalSee
Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
-
E.
typicalDefenseFormat
Indicates the usual or standard defensive arrangement, structure, or strategy typically employed in a given 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00953bc848190b83919f39d5ee37b |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.