Triple
T24848037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the lamplighter |
E621809
|
entity |
| Predicate | workMotivation |
P4937
|
FINISHED |
| Object | obedience to orders |
—
|
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: obedience to orders | Statement: [the lamplighter, workMotivation, obedience to orders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workMotivation Context triple: [the lamplighter, workMotivation, obedience to orders]
-
A.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
B.
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.
-
C.
motivated
chosen
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
-
D.
focusesOnWork
Indicates that an entity directs its attention, effort, or primary activity toward work-related tasks or responsibilities.
-
E.
motivatedByGoal
Indicates that an action, behavior, or state occurs as a result of an intention to achieve a specific goal or desired outcome.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.