Triple
T30160783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Nightingale Sang in Berkeley Square |
E766657
|
entity |
| Predicate | placeInTitleLocation |
P59484
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [A Nightingale Sang in Berkeley Square, placeInTitleLocation, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInTitleLocation Context triple: [A Nightingale Sang in Berkeley Square, placeInTitleLocation, London]
-
A.
hasPlaceInTitle
chosen
Indicates that a work’s title explicitly includes the name of a place as part of the title.
-
B.
associatedTitleLocation
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
-
C.
hasTitleLocation
Indicates that an entity’s title or heading is associated with a specific location or position (e.g., in a document, interface, or spatial layout).
-
D.
hasTitleCharacterLocation
Indicates that a title or heading is associated with a specific character’s location within a text or media.
-
E.
alternateNameForPlaceInTitle
Indicates that a work’s title uses an alternative name or variant designation for a particular place.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:21 p.m.