Triple
T24785664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Homes |
E620109
|
entity |
| Predicate | hasSeriesUniverse |
P119254
|
FINISHED |
| Object | Folly universe |
—
|
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: Folly universe | Statement: [Broken Homes, hasSeriesUniverse, Folly universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesUniverse Context triple: [Broken Homes, hasSeriesUniverse, Folly universe]
-
A.
hasFictionalUniverseType
Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
-
B.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
C.
hasFictionalSeries
Indicates that one entity is a fictional series that another entity possesses, is associated with, or is the creator/owner of.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
sharesFictionalUniverseWith
chosen
Indicates that two entities are set within the same fictional universe or continuity, such that their stories coexist in a shared narrative world.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 4:45 a.m.