Triple
T24429256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunnydale High School |
E615944
|
entity |
| Predicate | hasSecretLocation |
P108773
|
FINISHED |
| Object | Hellmouth beneath the library |
—
|
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: Hellmouth beneath the library | Statement: [Sunnydale High School, hasSecretLocation, Hellmouth beneath the library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretLocation Context triple: [Sunnydale High School, hasSecretLocation, Hellmouth beneath the library]
-
A.
hasSecretArea
chosen
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
B.
hasSecretFacility
Indicates that an entity possesses or controls a hidden or undisclosed facility.
-
C.
hasSecretExit
Indicates that something includes or is connected to a hidden or concealed way out.
-
D.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
E.
hidingPlace
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296aab8948190b9cb869bab71fb4c |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.