Triple
T20663118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Through the Night |
E507809
|
entity |
| Predicate | hasAmateurSleuth |
P63938
|
FINISHED |
| Object | Alvirah Meehan |
—
|
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: Alvirah Meehan | Statement: [All Through the Night, hasAmateurSleuth, Alvirah Meehan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmateurSleuth Context triple: [All Through the Night, hasAmateurSleuth, Alvirah Meehan]
-
A.
hasClericalDetective
Indicates that an entity includes or is associated with a detective who is also a member of the clergy.
-
B.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
C.
hasFictionalDetective
chosen
Indicates that one entity (typically a work or series) features or includes a fictional detective character as part of its content.
-
D.
notableSuspect
Indicates that an individual is a particularly significant or prominent suspect in relation to an event, case, or investigation.
-
E.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2f4872481908858eb88ce89dd47 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.