Triple
T31783993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Falls |
E811278
|
entity |
| Predicate | hasPlaceInFictionalUniverse |
P138873
|
FINISHED |
| Object | Rebus universe |
—
|
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: Rebus universe | Statement: [The Falls, hasPlaceInFictionalUniverse, Rebus universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceInFictionalUniverse Context triple: [The Falls, hasPlaceInFictionalUniverse, Rebus universe]
-
A.
isSetInFictionalUniverse
chosen
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
B.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
D.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
E.
hasFictionalUniverseType
Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 30, 2026, 11:37 p.m.