Triple
T27782061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Plum |
E699356
|
entity |
| Predicate | appearsInVariant |
P174683
|
FINISHED |
| Object | Master Detective 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: Master Detective Clue | Statement: [Professor Plum, appearsInVariant, Master Detective Clue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInVariant Context triple: [Professor Plum, appearsInVariant, Master Detective Clue]
-
A.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
B.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
C.
hasVariantDepiction
Indicates that one entity is depicted in an alternative or modified visual form relative to another depiction of the same subject.
-
D.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
- F. None of above. chosen
Provenance (4 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_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 27, 2026, 5:10 p.m.