Triple
T22599664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agent 47 |
E574778
|
entity |
| Predicate | hasBarcodeLocation |
P148886
|
FINISHED |
| Object | back of head |
—
|
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: back of head | Statement: [Agent 47, hasBarcodeLocation, back of head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBarcodeLocation Context triple: [Agent 47, hasBarcodeLocation, back of head]
-
A.
hasBarcode
Indicates that an entity is associated with or identified by a specific barcode.
-
B.
barLocation
Indicates that one entity is the physical location or venue where a bar is situated or operates in relation to another entity.
-
C.
hasReceiverLocation
Indicates that an entity serves as the destination or location where something is received by another party.
-
D.
hasNationalLocationCode
Indicates that an entity is associated with a specific national location code that identifies its location within a country’s coding system.
-
E.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626b5f5481909a104088d1c96720 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 2:50 p.m.