Triple
T5453999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hiding Place (novel) |
E122434
|
entity |
| Predicate | fictional |
P14491
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Hiding Place (novel), fictional, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictional Context triple: [The Hiding Place (novel), fictional, true]
-
A.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
B.
fictionalMaterial
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
-
C.
fictionalizationOf
Indicates that one entity is a fictional or dramatized representation, adaptation, or reimagining of another (typically real or earlier) entity or event.
-
D.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
E.
fictionalStatus
chosen
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.