Triple
T973639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mounted Unit |
E21000
|
entity |
| Predicate | supportsPoliceFunction |
P17162
|
FINISHED |
| Object | public order maintenance |
—
|
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: public order maintenance | Statement: [Mounted Unit, supportsPoliceFunction, public order maintenance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPoliceFunction Context triple: [Mounted Unit, supportsPoliceFunction, public order maintenance]
-
A.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
B.
lawEnforcementResponse
Indicates the actions or measures taken by law enforcement agencies in reaction to an incident, behavior, or situation.
-
C.
hasCivicFunction
chosen
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
D.
partOfOfficerLine
Indicates that one entity is a member or segment of a sequence or formation of officers.
-
E.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 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.