Triple
T851469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son bridge |
E18393
|
entity |
| Predicate | statusDuringOperationMarketGarden |
P20598
|
FINISHED |
| Object | destroyed by German forces |
—
|
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: destroyed by German forces | Statement: [Son bridge, statusDuringOperationMarketGarden, destroyed by German forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringOperationMarketGarden Context triple: [Son bridge, statusDuringOperationMarketGarden, destroyed by German forces]
-
A.
objectiveInOperationMarketGarden
Indicates that something served as an objective or target within Operation Market Garden.
-
B.
operatingStatus
Indicates whether an entity is currently functioning, active, or in service versus inactive, closed, or out of service.
-
C.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
D.
marketOperatedBy
Indicates that a market is managed, controlled, or run by a specific operator or organization.
-
E.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac22de288190913714d41e5a8e12 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.