Triple
T9502052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilary Cummins |
E229165
|
entity |
| Predicate | keyElementOf |
P5688
|
FINISHED |
| Object | mystery in The Beast with Five Fingers |
—
|
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: mystery in The Beast with Five Fingers | Statement: [Hilary Cummins, keyElementOf, mystery in The Beast with Five Fingers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyElementOf Context triple: [Hilary Cummins, keyElementOf, mystery in The Beast with Five Fingers]
-
A.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
B.
keyComponent
chosen
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
C.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
-
D.
keyIndex
Indicates the position or numerical index assigned to a specific key within an ordered set or collection of keys.
-
E.
keyCol
Indicates that one column in a dataset or table serves as a key used to uniquely identify or link records.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983d4b708190a4dfef1246986a26 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.