Triple
T27782067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Plum |
E699356
|
entity |
| Predicate | typicalMotiveType |
P6699
|
FINISHED |
| Object | academic rivalry |
—
|
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: academic rivalry | Statement: [Professor Plum, typicalMotiveType, academic rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMotiveType Context triple: [Professor Plum, typicalMotiveType, academic rivalry]
-
A.
depictsMotive
Indicates that one entity visually represents or illustrates the motive, intention, or underlying reason associated with another entity or action.
-
B.
motive
chosen
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
C.
repeatedMotive
Indicates that the same motive recurs multiple times within a work, sequence, or context.
-
D.
legendaryMotive
Indicates a motive or driving reason behind an action or state that is regarded as legendary, iconic, or of mythic significance.
-
E.
typicalLoanPurpose
Indicates the usual or intended purpose for which a loan is taken or used.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 27, 2026, 5:10 p.m.