Triple
T973122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City auxiliary police officers |
E20987
|
entity |
| Predicate | isSworn |
P16364
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [New York City auxiliary police officers, isSworn, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSworn Context triple: [New York City auxiliary police officers, isSworn, true]
-
A.
hasSwornStatus
chosen
Indicates that an entity is formally bound by an oath or sworn commitment, reflecting an official or pledged status in relation to another entity or role.
-
B.
oathSwornBefore
Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
-
C.
mayBeAffirmedRatherThanSworn
Indicates that a statement or testimony can be confirmed by affirmation instead of being given under a formal oath.
-
D.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
E.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b45f28f081908d41b2d7f353708d |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.