Triple
T31692635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastland School |
E808832
|
entity |
| Predicate | operatedByInStory |
P129228
|
FINISHED |
| Object | headmistress and staff (fictional) |
—
|
LITERAL FINISHED |
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: headmistress and staff (fictional) | Statement: [Eastland School, operatedByInStory, headmistress and staff (fictional)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByInStory Context triple: [Eastland School, operatedByInStory, headmistress and staff (fictional)]
-
A.
ownerInStory
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
B.
operatedByCharacter
chosen
Indicates that an operation, action, or process is carried out or controlled by a specific character.
-
C.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
D.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
E.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 30, 2026, 11:09 p.m.