Triple
T33878836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moor House |
E868428
|
entity |
| Predicate | providesRefugeFor |
P95817
|
FINISHED |
| Object | Jane Eyre |
—
|
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: Jane Eyre | Statement: [Moor House, providesRefugeFor, Jane Eyre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesRefugeFor Context triple: [Moor House, providesRefugeFor, Jane Eyre]
-
A.
takenAsRefugeBy
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
-
B.
designatedAsRefuge
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
C.
areaServedAsShelterFor
chosen
Indicates that one entity functioned as a shelter or refuge for another entity, providing protection or a safe place.
-
D.
seeksRefugeAt
Indicates that one entity goes to or turns to another entity or location for safety, protection, or shelter, especially in a time of danger or distress.
-
E.
tookRefugeWith
Indicates that one entity sought safety, protection, or shelter by going to and staying 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_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:48 a.m.