Triple
T32967447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man from Byzantium |
E843410
|
entity |
| Predicate | associatedPlaceInTitle |
P59484
|
FINISHED |
| Object | Byzantium |
E756048
|
NE 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: Byzantium | Statement: [The Man from Byzantium, associatedPlaceInTitle, Byzantium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPlaceInTitle Context triple: [The Man from Byzantium, associatedPlaceInTitle, Byzantium]
-
A.
associatedTitleLocation
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
hasPlaceInTitle
chosen
Indicates that a work’s title explicitly includes the name of a place as part of the title.
-
D.
alternateNameForPlaceInTitle
Indicates that a work’s title uses an alternative name or variant designation for a particular place.
-
E.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
- F. None of above.
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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34dabba3f48190a95eed6422cc1f7e |
completed | June 19, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:21 a.m.