Triple
T36296801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sombertown school |
E893391
|
entity |
| Predicate | hasFictionalStudents |
P198418
|
FINISHED |
| Object | children of Sombertown |
—
|
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: children of Sombertown | Statement: [Sombertown school, hasFictionalStudents, children of Sombertown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalStudents Context triple: [Sombertown school, hasFictionalStudents, children of Sombertown]
-
A.
hasFictionalStudentBodyType
Indicates that an entity is characterized by a type or category of student body that exists in a fictional or imaginary context.
-
B.
hasFictionalSchool
Indicates that an entity is associated with or contains a school that exists only within a fictional or imaginary context.
-
C.
hasStudentFictional
chosen
Indicates that an entity has, is associated with, or is characterized by a student who is fictional rather than real.
-
D.
hasStudentCharacter
Indicates that an entity possesses or is associated with a character or role in the capacity of a student.
-
E.
hasFictionalStaffMember
Indicates that an entity includes or employs a staff member who is 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 3, 2026, 4:09 p.m.