Triple
T25826656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Stewart tartan |
E650548
|
entity |
| Predicate | commonlyWornBy |
P84687
|
FINISHED |
| Object | Scottish regiments |
—
|
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: Scottish regiments | Statement: [Royal Stewart tartan, commonlyWornBy, Scottish regiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyWornBy Context triple: [Royal Stewart tartan, commonlyWornBy, Scottish regiments]
-
A.
typicallyWornBy
chosen
Indicates that something (such as an item or garment) is most commonly or characteristically worn by a particular type of person or group.
-
B.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
C.
typicalWear
Indicates that one entity is commonly or characteristically worn by the other in typical situations or contexts.
-
D.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
E.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 7:36 a.m.