Triple
T30635444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Prentiss |
E779828
|
entity |
| Predicate | temporarilyLeavesBAU |
P170775
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Emily Prentiss, temporarilyLeavesBAU, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyLeavesBAU Context triple: [Emily Prentiss, temporarilyLeavesBAU, yes]
-
A.
leaveProtection
Indicates that an entity stops providing protection or removes a protective status from another entity.
-
B.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
C.
usedBriefly
Indicates that an entity made short-term or momentary use of another entity or resource.
-
D.
temporaryIncapacityDeclared
Indicates that an official determination has been made that an entity is temporarily unable to perform its usual duties or functions.
-
E.
hasTemporaryStation
Indicates that an entity is associated with a station or facility that is intended to be used only for a limited or non-permanent period.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:28 p.m.