Triple
T34899709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Gordon |
E1006545
|
entity |
| Predicate | settingPlaceOfWork |
P1527
|
FINISHED |
| Object | small American town |
—
|
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: small American town | Statement: [Louise Gordon, settingPlaceOfWork, small American town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingPlaceOfWork Context triple: [Louise Gordon, settingPlaceOfWork, small American town]
-
A.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
B.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
C.
placeInWork
Indicates that one entity is located or occurs within the spatial or structural context of another entity in a work.
-
D.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
E.
setInPlaceOfWork
Indicates that an entity is assigned or located at a specific place of work in place of another entity.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4 p.m.