Triple
T25352032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madeleine McCann disappearance |
E635712
|
entity |
| Predicate | policeOperation |
P76022
|
FINISHED |
| Object | Operation Grange |
—
|
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: Operation Grange | Statement: [Madeleine McCann disappearance, policeOperation, Operation Grange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeOperation Context triple: [Madeleine McCann disappearance, policeOperation, Operation Grange]
-
A.
policeOperationName
chosen
Indicates the official name assigned to a specific police operation or law enforcement action.
-
B.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
C.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
-
D.
rescueOperation
Indicates an action where one entity undertakes efforts to save or free another entity from danger, harm, or a threatening situation.
-
E.
militaryOperationName
Indicates the specific named military operation associated with an action, event, 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:34 p.m.