Triple
T21348150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darcy Scott |
E526396
|
entity |
| Predicate | drivingForceInStory |
P24726
|
FINISHED |
| Object | passion for dancing |
—
|
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: passion for dancing | Statement: [Darcy Scott, drivingForceInStory, passion for dancing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingForceInStory Context triple: [Darcy Scott, drivingForceInStory, passion for dancing]
-
A.
drivingForce
chosen
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
B.
drivingCharacter
Indicates that one character is operating or controlling a vehicle or mode of transportation.
-
C.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
-
D.
drivingChallenge
Indicates a situation in which driving is made difficult or demanding due to conditions, obstacles, or required skills.
-
E.
isNarrativeDriven
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baab4e081908916a289c607cf3a |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:01 p.m.