Triple
T7138611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Formers of St. Clare's |
E166378
|
entity |
| Predicate | hasFictionalTime |
P60994
|
FINISHED |
| Object | school term |
—
|
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: school term | Statement: [Fifth Formers of St. Clare's, hasFictionalTime, school term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalTime Context triple: [Fifth Formers of St. Clare's, hasFictionalTime, school term]
-
A.
fictionalTime
chosen
Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
-
B.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
hasFictionalProperty
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e694cc3c81908b0d54c2496a0722 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.