Triple
T19489896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grey Fairy Book |
E487619
|
entity |
| Predicate | includesTaleOrigin |
P120146
|
FINISHED |
| Object | French folklore |
—
|
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: French folklore | Statement: [The Grey Fairy Book, includesTaleOrigin, French folklore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTaleOrigin Context triple: [The Grey Fairy Book, includesTaleOrigin, French folklore]
-
A.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
B.
includesFolklore
chosen
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
C.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
D.
associatedTale
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
E.
hasStandaloneTales
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348d43448190bf83680522b8b415 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.