Triple
T8450139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Algernon Edwards |
E199778
|
entity |
| Predicate | secretClinicLocation |
P43162
|
FINISHED |
| Object | basement of The Knickerbocker Hospital |
—
|
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: basement of The Knickerbocker Hospital | Statement: [Dr. Algernon Edwards, secretClinicLocation, basement of The Knickerbocker Hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretClinicLocation Context triple: [Dr. Algernon Edwards, secretClinicLocation, basement of The Knickerbocker Hospital]
-
A.
unveiledLocation
Indicates that an entity has revealed or made known the location of another entity or object.
-
B.
hidingPlace
chosen
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
-
C.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44707b88190b3d8b30c45ef4496 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.