Triple
T20359599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lesson |
E496741
|
entity |
| Predicate | recurringMotive |
P112503
|
FINISHED |
| Object | linguistic confusion |
—
|
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: linguistic confusion | Statement: [The Lesson, recurringMotive, linguistic confusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringMotive Context triple: [The Lesson, recurringMotive, linguistic confusion]
-
A.
repeatedMotive
chosen
Indicates that the same motive recurs multiple times within a work, sequence, or context.
-
B.
recurrence
Indicates that an event, condition, or state happens again or repeatedly over time, often after a period of absence or resolution.
-
C.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
D.
laterMotivation
Indicates that one event, state, or action serves as a motivation or reason for another event, state, or action that occurs later in time.
-
E.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678573fc481908bf257e6ed41d750 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.