Triple
T33166535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senio River |
E848901
|
entity |
| Predicate | usedAsMilitaryLine |
P195699
|
FINISHED |
| Object | Gothic Line |
—
|
NE NERFINISHED |
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: Gothic Line | Statement: [Senio River, usedAsMilitaryLine, Gothic Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMilitaryLine Context triple: [Senio River, usedAsMilitaryLine, Gothic Line]
-
A.
usedByBranchOfMilitary
Indicates that something is utilized or operated by a specific branch of a country's military forces.
-
B.
usesMilitaryUnit
Indicates that one entity employs, deploys, or otherwise makes operational use of a specific military unit.
-
C.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
-
D.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
-
E.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
- 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: May 1, 2026, 1:28 a.m.