Triple
T24374126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindanise battle |
E614419
|
entity |
| Predicate | opponentDescription |
P148921
|
FINISHED |
| Object | local Estonian forces |
—
|
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: local Estonian forces | Statement: [Lindanise battle, opponentDescription, local Estonian forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentDescription Context triple: [Lindanise battle, opponentDescription, local Estonian forces]
-
A.
opponentsDescription
chosen
Indicates that a description is provided of the opposing side or competitors in a conflict, contest, or disagreement.
-
B.
opponentTitle
Indicates that the object is the formal title or designation held by an opponent in a competitive or adversarial context.
-
C.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
D.
viewCharacterizationByOpponents
Indicates how opponents characterize or portray a particular view or position.
-
E.
opponentForceCharacteristic
Indicates a characteristic or attribute that describes the nature, capability, or condition of an opposing force.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d67404819091281523ef12b9b5 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.