Triple
T27782036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Plum |
E699356
|
entity |
| Predicate | isPrimarySuspectIn |
P166117
|
FINISHED |
| Object | Clue |
—
|
NE NERFINISHED |
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: Clue | Statement: [Professor Plum, isPrimarySuspectIn, Clue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimarySuspectIn Context triple: [Professor Plum, isPrimarySuspectIn, Clue]
-
A.
hasSuspect
chosen
Indicates that an entity is identified or considered as a suspect in relation to another entity or incident.
-
B.
isSuspiciousOf
Indicates that one entity believes another entity or situation may be untrustworthy, harmful, or involved in wrongdoing.
-
C.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
D.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
E.
sawAsPrimary
Indicates that one entity regarded another entity as the main or most important option, focus, or choice among alternatives.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 5:10 p.m.