Triple
T23813213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loch Sloy |
E589915
|
entity |
| Predicate | hasBattleCry |
P10430
|
FINISHED |
| Object | Loch Sloy |
—
|
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: Loch Sloy | Statement: [Loch Sloy, hasBattleCry, Loch Sloy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattleCry Context triple: [Loch Sloy, hasBattleCry, Loch Sloy]
-
A.
battleCryAssociated
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
chosen
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.
clanSlogan
Indicates the motto or slogan associated with a particular clan.
-
E.
hasFightingMoniker
Indicates that an entity is known by a specific nickname or title used in a fighting or combat 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7a911f481909c8a98a5aec72b4b |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:57 p.m.