Triple
T12532807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isonzo River |
E299610
|
entity |
| Predicate | numberOfMajorBattles |
P105747
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Isonzo River, numberOfMajorBattles, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMajorBattles Context triple: [Isonzo River, numberOfMajorBattles, 12]
-
A.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
B.
timeOfMajorBattle
Indicates the specific time at which a major battle took place.
-
C.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
D.
isLargestBattleIn
Indicates that a battle is the largest (by scale, size, or impact) among all battles occurring within a specified context, such as a war, campaign, region, or time period.
-
E.
notableBattlefield
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.