Triple
T28443603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craig Gilner |
E715777
|
entity |
| Predicate | checksInto |
P164731
|
FINISHED |
| Object | psychiatric ward |
—
|
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: psychiatric ward | Statement: [Craig Gilner, checksInto, psychiatric ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checksInto Context triple: [Craig Gilner, checksInto, psychiatric ward]
-
A.
checkedDuring
Indicates that an entity was examined, inspected, or verified at a specific time or during a particular event or process.
-
B.
checkedBy
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
C.
checksInformationFrom
Indicates that one entity verifies, reviews, or consults information originating from another entity.
-
D.
providedCheckBy
Indicates that a check or verification was supplied or performed by a particular agent or entity.
-
E.
requiresCheckIn
Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
- F. None of above. chosen
Provenance (4 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:47 a.m.