Triple
T32715620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Hand plot |
E836513
|
entity |
| Predicate | hasLocationOnDay |
P196365
|
FINISHED |
| Object | Appel Quay |
—
|
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: Appel Quay | Statement: [Black Hand plot, hasLocationOnDay, Appel Quay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationOnDay Context triple: [Black Hand plot, hasLocationOnDay, Appel Quay]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
locatedAtTime
Indicates that a location relationship holds during a specific time or time interval.
-
C.
hasLocalityDay
Indicates that a specific day is officially designated or observed within a particular locality or municipality.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
E.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: May 1, 2026, 1:11 a.m.