Triple
T35443247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cowra Breakout (1984 miniseries) |
E1024409
|
entity |
| Predicate | basedOnEventLocation |
P49732
|
FINISHED |
| Object | Cowra, New South Wales |
—
|
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: Cowra, New South Wales | Statement: [The Cowra Breakout (1984 miniseries), basedOnEventLocation, Cowra, New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEventLocation Context triple: [The Cowra Breakout (1984 miniseries), basedOnEventLocation, Cowra, New South Wales]
-
A.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
B.
locationOfEventOrganized
Indicates the place where a particular organized event is held or takes place.
-
C.
locationOfEventDescribed
chosen
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
D.
tookPlaceAtLocation
Indicates that an event or action occurred at a specific location.
-
E.
locatedInProvinceOfOperatedVenue
Indicates that the province specified is the administrative region in which the operated venue is geographically located.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
Created at: May 3, 2026, 4:04 p.m.