Triple
T3438787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Paris (845) |
E72518
|
entity |
| Predicate | approximateStrengthAttacker |
P2981
|
FINISHED |
| Object | about 120 ships |
—
|
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: about 120 ships | Statement: [siege of Paris (845), approximateStrengthAttacker, about 120 ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateStrengthAttacker Context triple: [siege of Paris (845), approximateStrengthAttacker, about 120 ships]
-
A.
attackerStrength
Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
-
B.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
C.
opponentStrength
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
-
D.
hasDefenderStrength
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
E.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f6de1481909b789f4b0e1113d3 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.