Triple
T30287055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Darley |
E770265
|
entity |
| Predicate | placeOfWorkSignificance |
P1527
|
FINISHED |
| Object | Dublin |
—
|
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: Dublin | Statement: [Frederick Darley, placeOfWorkSignificance, Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfWorkSignificance Context triple: [Frederick Darley, placeOfWorkSignificance, Dublin]
-
A.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
B.
parentWorkSignificance
Indicates the degree of importance or influence that a parent work has on the related work or context.
-
C.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
-
D.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
-
E.
workAt
Indicates that an entity is employed by or performs work for a particular organization, company, or 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 7:46 p.m.