Triple
T28048105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Boyce |
E708738
|
entity |
| Predicate | placeOfRearrest |
P24149
|
FINISHED |
| Object | Port Angeles, Washington, United States |
—
|
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: Port Angeles, Washington, United States | Statement: [Christopher Boyce, placeOfRearrest, Port Angeles, Washington, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfRearrest Context triple: [Christopher Boyce, placeOfRearrest, Port Angeles, Washington, United States]
-
A.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
B.
arrestedAt
chosen
Indicates that an entity was apprehended or taken into custody at a specific location or during a specific event or time.
-
C.
placeOfDetention
Indicates the location or facility where an entity is or was held in detention.
-
D.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
-
E.
arrestedWith
Indicates that two or more individuals were arrested at the same time and in connection with the same incident or operation.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 8:31 p.m.