Triple
T11609422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Jasna Góra |
E275343
|
entity |
| Predicate | strengthDefendersApprox |
P12310
|
FINISHED |
| Object | about 160 soldiers |
—
|
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 160 soldiers | Statement: [Siege of Jasna Góra, strengthDefendersApprox, about 160 soldiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthDefendersApprox Context triple: [Siege of Jasna Góra, strengthDefendersApprox, about 160 soldiers]
-
A.
hasDefenderStrength
chosen
Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
-
B.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
C.
totalStrength
Indicates the overall magnitude or combined level of strength associated with an entity or group of entities.
-
D.
attackerStrength
Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
-
E.
opponentStrength
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04231d08190b8a07cd977d11ffa |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.