Triple
T973103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City auxiliary police officers |
E20987
|
entity |
| Predicate | performsActivity |
P19746
|
FINISHED |
| Object | patrols |
—
|
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: patrols | Statement: [New York City auxiliary police officers, performsActivity, patrols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsActivity Context triple: [New York City auxiliary police officers, performsActivity, patrols]
-
A.
performsAt
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
B.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
E.
exportActivity
Indicates an action where goods, services, or data are sent out from one entity or region to another for trade or distribution across borders.
- 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.