Triple
T25707279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery of the Missing Necklace |
E644625
|
entity |
| Predicate | hasDetectiveGroupName |
P113419
|
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 Missing Necklace, hasDetectiveGroupName, Five Find-Outers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectiveGroupName Context triple: [The Mystery of the Missing Necklace, hasDetectiveGroupName, Five Find-Outers]
-
A.
identifiesGroup
Indicates that one entity serves to recognize, label, or distinguish another entity as belonging to a particular group or category.
-
B.
hasCharacterGroupName
chosen
Indicates that an entity is associated with a specific name identifying a group of characters.
-
C.
hasFanGroupName
Indicates that an entity has a specific name for its fan group or fandom.
-
D.
hasFamilyNameInGroupName
Indicates that a group’s name includes or is derived from the family name of a person associated with that group.
-
E.
hasCrimeGroup
Indicates a relationship where an entity is associated with, belongs to, or is controlled by a particular criminal group or organization.
- 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_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 9:06 p.m.