Triple
T28127696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There You Are |
E710973
|
entity |
| Predicate | hasSourceMaterialStatus |
P60201
|
FINISHED |
| Object | based on an unfinished novel |
—
|
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: based on an unfinished novel | Statement: [There You Are, hasSourceMaterialStatus, based on an unfinished novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceMaterialStatus Context triple: [There You Are, hasSourceMaterialStatus, based on an unfinished novel]
-
A.
hasSourceMaterial
Indicates that something is derived from, based on, or created using a particular source material.
-
B.
materialStatus
chosen
Indicates the current state or condition of a material, such as its availability, usage, or processing stage.
-
C.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
D.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
E.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 9:21 p.m.