Triple
T25487244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craigellachie |
E638745
|
entity |
| Predicate | isBattleCryOf |
P146223
|
FINISHED |
| Object | Clan Grant |
—
|
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: Clan Grant | Statement: [Craigellachie, isBattleCryOf, Clan Grant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBattleCryOf Context triple: [Craigellachie, isBattleCryOf, Clan Grant]
-
A.
battleCryAssociated
chosen
Indicates a relationship where a specific battle cry is linked or attributed to a particular entity, such as a person, group, or event.
-
B.
warCry
Indicates a relationship where an entity utters or performs a loud, rallying shout or chant intended to inspire allies or intimidate opponents, typically in a conflict or competitive context.
-
C.
flagshipDuringBattle
Indicates that one entity serves as the primary command ship for another entity during a specific battle or military engagement.
-
D.
isWarHeroOf
Indicates that one entity is recognized as a war hero in relation to, or on behalf of, another entity (such as a country, group, or cause).
-
E.
حمله
Indicates an aggressive action in which one entity attacks, assaults, or launches an offensive against another.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f77d26488190898b7befa111282b |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:33 p.m.