Triple
T1507092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustav Line |
E33924
|
entity |
| Predicate | brokeBy |
P23233
|
FINISHED |
| Object | Allied forces in 1944 |
—
|
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: Allied forces in 1944 | Statement: [Gustav Line, brokeBy, Allied forces in 1944]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeBy Context triple: [Gustav Line, brokeBy, Allied forces in 1944]
-
A.
isBrokenBy
Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
-
B.
spontaneouslyBrokenBy
Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
-
C.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
D.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
E.
dismantledBy
chosen
Indicates that something has been taken apart, disassembled, or broken down by a particular agent or 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.