Triple
T1430392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 51st (Highland) Division |
E30430
|
entity |
| Predicate | ethnicOrCulturalIdentity |
P194
|
FINISHED |
| Object | Scottish Highland |
—
|
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: Scottish Highland | Statement: [51st (Highland) Division, ethnicOrCulturalIdentity, Scottish Highland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOrCulturalIdentity Context triple: [51st (Highland) Division, ethnicOrCulturalIdentity, Scottish Highland]
-
A.
ethnoreligiousIdentity
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
-
B.
ethnicOrigin
chosen
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
D.
recognizedAsMinorityIn
Indicates that an entity is officially acknowledged or classified as belonging to a minority group within a specified context or jurisdiction.
-
E.
ethnicCategoryIn
Indicates that an entity belongs to or is classified within a specified ethnic category 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.