Triple
T32377229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everything That Glitters |
E827322
|
entity |
| Predicate | isOnEP |
P22078
|
FINISHED |
| Object | Fear of God II: Let Us Pray |
—
|
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: Fear of God II: Let Us Pray | Statement: [Everything That Glitters, isOnEP, Fear of God II: Let Us Pray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnEP Context triple: [Everything That Glitters, isOnEP, Fear of God II: Let Us Pray]
-
A.
isEPBy
Indicates that one entity is the endpoint or end position defined, determined, or reached by another entity or process.
-
B.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
C.
hasEP
chosen
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
D.
isPlayOn
Indicates that one entity is a pun, wordplay, or creative variation based on the form or meaning of another entity.
-
E.
isKeyEpisodeIn
Indicates that an episode plays a crucial or defining role within a larger narrative, season, or series.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:51 a.m.