Triple
T22221173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYPD Lieutenant |
E549210
|
entity |
| Predicate | shiftType |
P86194
|
FINISHED |
| Object | may work day tours |
—
|
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: may work day tours | Statement: [NYPD Lieutenant, shiftType, may work day tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftType Context triple: [NYPD Lieutenant, shiftType, may work day tours]
-
A.
shiftPattern
chosen
Indicates a recurring schedule or arrangement that defines how work or activity shifts are organized over time.
-
B.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
C.
shiftsWhen
Indicates that one state, condition, or configuration changes to another under specified circumstances or triggers.
-
D.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
E.
marksShiftToward
Indicates a change or transition from one state, condition, or position toward another, highlighting the direction or trend of that shift.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b90b1dc81908fee5fab8d5d14a2 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.