Triple
T31530263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campaigns against Great Moravia |
E804456
|
entity |
| Predicate | defenderState |
P179253
|
FINISHED |
| Object | Great Moravia |
—
|
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: Great Moravia | Statement: [Campaigns against Great Moravia, defenderState, Great Moravia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenderState Context triple: [Campaigns against Great Moravia, defenderState, Great Moravia]
-
A.
defendingState
Indicates that one entity is acting to protect or defend another entity from a threat, attack, or accusation.
-
B.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
defenderBase
Indicates that one entity serves as the primary defensive location or stronghold associated with another entity.
-
E.
defenderNotablyStiffArmed
Indicates that a defender forcefully extended their arm to fend off or block an opponent in a particularly notable or impactful way.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 30, 2026, 10 p.m.