Triple
T25580233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Town Highlanders |
E641220
|
entity |
| Predicate | hasCeremonialItem |
P7123
|
FINISHED |
| Object | kilt |
—
|
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: kilt | Statement: [Cape Town Highlanders, hasCeremonialItem, kilt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeremonialItem Context triple: [Cape Town Highlanders, hasCeremonialItem, kilt]
-
A.
haveCeremonialHead
Indicates that one entity serves as the formal or symbolic head or leader of another entity, typically without holding full executive power.
-
B.
isCeremonial
Indicates that something is associated with, intended for, or used in a formal ceremony or ritual rather than for ordinary or practical purposes.
-
C.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
D.
ceremonialRequirement
Indicates that one entity must perform or satisfy a specified ritual or formal procedure as a necessary condition for another entity, event, or status.
-
E.
ceremonialFeatures
Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 21, 2026, 4:11 p.m.