Triple
T34999609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall Farm |
E1009632
|
entity |
| Predicate | managedByCharacter |
P117528
|
FINISHED |
| Object | Mrs. Poyser |
—
|
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: Mrs. Poyser | Statement: [Hall Farm, managedByCharacter, Mrs. Poyser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedByCharacter Context triple: [Hall Farm, managedByCharacter, Mrs. Poyser]
-
A.
managedByFictionalCharacter
chosen
Indicates that an entity is overseen, directed, or run under the authority or control of a fictional character.
-
B.
operatedByCharacter
Indicates that an operation, action, or process is carried out or controlled by a specific character.
-
C.
modifiedByCharacter
Indicates that something has been altered or influenced through the actions or behavior of a particular character.
-
D.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
E.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:01 p.m.