Triple
T8189007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Isonzo |
E191257
|
entity |
| Predicate | numberOfEngagements |
P2438
|
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: [Battle of the Isonzo, numberOfEngagements, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfEngagements Context triple: [Battle of the Isonzo, numberOfEngagements, 12]
-
A.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
B.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
C.
numberOfEvents
chosen
Indicates the quantity or count of events associated with a given entity or context.
-
D.
isMajorEngagementIn
Indicates that an event or action constitutes a primary or significant engagement occurring within a specified context, setting, or larger operation.
-
E.
numberOfCampaignsApprox
Indicates an approximate count of campaigns associated with or relevant to a given 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.