Triple
T33255079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irving Stone |
E851352
|
entity |
| Predicate | basedOnExtensiveResearch |
P13412
|
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: [Irving Stone, basedOnExtensiveResearch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnExtensiveResearch Context triple: [Irving Stone, basedOnExtensiveResearch, true]
-
A.
researchBasis
Indicates that one entity serves as the foundational research, evidence, or scholarly support upon which another entity is based or justified.
-
B.
usedResearchFrom
chosen
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
C.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
-
D.
appliesResearchTo
Indicates that an entity uses or implements research findings, methods, or insights in relation to another entity, context, or problem.
-
E.
conductedResearchOn
Indicates that an entity has performed or carried out research concerning another entity or topic.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 1:31 a.m.