Triple
T14969499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Maxwell |
E373278
|
entity |
| Predicate | clanBattleCry |
P10430
|
FINISHED |
| Object | Maxwell and Avenge |
—
|
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: Maxwell and Avenge | Statement: [Clan Maxwell, clanBattleCry, Maxwell and Avenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanBattleCry Context triple: [Clan Maxwell, clanBattleCry, Maxwell and Avenge]
-
A.
clanSlogan
Indicates the motto or slogan associated with a particular clan.
-
B.
clanRival
Indicates a hostile or competitive relationship between two clans, typically involving ongoing conflict, opposition, or rivalry.
-
C.
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.
-
D.
clanType
Indicates the specific category or classification of a clan within a broader clan system or hierarchy.
-
E.
clanCentre
Indicates that one entity serves as the central location, headquarters, or main base for a particular clan or group.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e44cb0819096e09f8026ef8174 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:49 a.m.