Triple
T36167254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cecily |
E1046040
|
entity |
| Predicate | setInPlaceOfWork |
P185047
|
FINISHED |
| Object | Zurich |
—
|
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: Zurich | Statement: [Cecily, setInPlaceOfWork, Zurich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInPlaceOfWork Context triple: [Cecily, setInPlaceOfWork, Zurich]
-
A.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
-
B.
placeInWork
Indicates that one entity is located or occurs within the spatial or structural context of another entity in a work.
-
C.
setInWorkBy
Indicates that something (such as a scene, event, or element) is situated or occurs within the context or setting of a particular work (such as a book, film, or other creative production).
-
D.
workInSet
Indicates that an entity performs work or has a role within a specified set, group, or collection.
-
E.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.