Triple
T30106409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roaratorio |
E765143
|
entity |
| Predicate | inspiredByForm |
P179046
|
FINISHED |
| Object | experimental 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: experimental novel | Statement: [Roaratorio, inspiredByForm, experimental novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredByForm Context triple: [Roaratorio, inspiredByForm, experimental novel]
-
A.
inspiredField
Indicates that one entity served as a source of inspiration or influence for the development, direction, or characteristics of a particular field or domain.
-
B.
envisionedForm
Indicates that one entity is the mental image, design, or conceptual form that another entity has imagined or planned.
-
C.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
originallyForm
Indicates that an entity existed in a particular initial shape, structure, or configuration before undergoing change or transformation.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 29, 2026, 7:09 p.m.