Triple
T33878163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branwell Brontë |
E868411
|
entity |
| Predicate | occupationAt |
P14167
|
FINISHED |
| Object | Luddendenfoot Railway Station |
—
|
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: Luddendenfoot Railway Station | Statement: [Branwell Brontë, occupationAt, Luddendenfoot Railway Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationAt Context triple: [Branwell Brontë, occupationAt, Luddendenfoot Railway Station]
-
A.
occupationOf
chosen
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
B.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
C.
hasOccupationOfResident
Indicates that one entity holds the role or status of being a resident in relation to another entity or context.
-
D.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
E.
orderedOccupationOf
Indicates that one entity holds a sequence-ordered list of occupations or roles associated with 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:48 a.m.