Triple
T26759976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowood School |
E674773
|
entity |
| Predicate | attendedByCharacter |
P1509
|
FINISHED |
| Object | Miss Temple |
—
|
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: Miss Temple | Statement: [Lowood School, attendedByCharacter, Miss Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendedByCharacter Context triple: [Lowood School, attendedByCharacter, Miss Temple]
-
A.
attendedByFictionalCharacter
Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
-
B.
attendedBy
chosen
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
C.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
D.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
E.
managedByFictionalCharacter
Indicates that an entity is overseen, directed, or run under the authority or control of a fictional 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:57 a.m.