Triple
T25707198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery of the Secret Room |
E644623
|
entity |
| Predicate | featuresDetectiveGroup |
P17143
|
FINISHED |
| Object | Five Find-Outers |
—
|
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: Five Find-Outers | Statement: [The Mystery of the Secret Room, featuresDetectiveGroup, Five Find-Outers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDetectiveGroup Context triple: [The Mystery of the Secret Room, featuresDetectiveGroup, Five Find-Outers]
-
A.
featuresPrivateDetective
Indicates that the subject includes or involves a private detective as a notable element or character.
-
B.
featuresDetectiveDuo
Indicates that the subject involves or centers around a pair of detectives working together as a team.
-
C.
detectiveType
Indicates that one entity is classified as a particular type or category of detective in relation to another entity.
-
D.
featuresGroup
chosen
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
E.
featuresCrimeSyndicate
Indicates that something includes, involves, or prominently depicts a crime syndicate as part of its content or structure.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 21, 2026, 9:06 p.m.