Triple
T36036645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmington detective squad |
E1042419
|
entity |
| Predicate | policeRankComposition |
P106599
|
FINISHED |
| Object | detectives |
—
|
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: detectives | Statement: [Farmington detective squad, policeRankComposition, detectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeRankComposition Context triple: [Farmington detective squad, policeRankComposition, detectives]
-
A.
policeRankStructure
Indicates the hierarchical ranking relationship that defines levels of authority and command within a police organization.
-
B.
policeRank
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
C.
enlistedRankComposition
chosen
Indicates the proportion or makeup of enlisted personnel ranks within a given group or organization.
-
D.
policeClassification
Indicates a categorization relationship where an entity is assigned a specific classification or status by a police or law-enforcement authority.
-
E.
commissionedRankStructure
Indicates that one entity defines or uses the hierarchical structure of commissioned ranks associated with another 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:07 p.m.