Triple
T30425116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense of Northern Italy |
E774003
|
entity |
| Predicate | notableDefensiveLine |
P122630
|
FINISHED |
| Object | Gothic Line |
E222991
|
NE 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: Gothic Line | Statement: [Defense of Northern Italy, notableDefensiveLine, Gothic Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDefensiveLine Context triple: [Defense of Northern Italy, notableDefensiveLine, Gothic Line]
-
A.
notableLinebacker
Indicates that the subject is a linebacker who is particularly prominent, distinguished, or well-recognized in that role.
-
B.
notableDefensivePlayersTeam1
Indicates that the referenced entities are notable defensive players who belong to or play for Team 1.
-
C.
notableDefensivePlayersTeam2
Indicates that the referenced entities are notable defensive players who belong to or play for the second team.
-
D.
primaryDefensiveLine
chosen
Indicates the main line of defense that first engages or protects against an opposing force or threat.
-
E.
notableDefenseman
Indicates that a person plays or played the position of defenseman in a sport and is recognized as particularly prominent, skilled, or distinguished in that role.
- F. None of above.
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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27ac1065d88190872a05b438a8b9c9 |
completed | June 9, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:06 p.m.