Triple
T37539515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronzebeard clan |
E933288
|
entity |
| Predicate | cityDefense |
P154840
|
FINISHED |
| Object | Ironforge Guard |
—
|
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: Ironforge Guard | Statement: [Bronzebeard clan, cityDefense, Ironforge Guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDefense Context triple: [Bronzebeard clan, cityDefense, Ironforge Guard]
-
A.
townDefendedBy
chosen
Indicates that a particular town is protected or guarded by a specified defending force or entity.
-
B.
shareDefenseStructure
Indicates that two or more entities utilize or are protected by the same defensive structure or system.
-
C.
primaryDefendedCity
Indicates that an entity served as the main or principal city that another entity was responsible for defending.
-
D.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
E.
typicalDefenseLocation
Indicates the usual or most common place where a defensive action, structure, or system is positioned or deployed.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.