Triple
T15613521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant (LAPD rank) |
E375356
|
entity |
| Predicate | supervisesRank |
P9418
|
FINISHED |
| Object | Sergeant (LAPD rank) |
—
|
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: Sergeant (LAPD rank) | Statement: [Lieutenant (LAPD rank), supervisesRank, Sergeant (LAPD rank)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisesRank Context triple: [Lieutenant (LAPD rank), supervisesRank, Sergeant (LAPD rank)]
-
A.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
-
B.
canSupervise
chosen
Indicates that one entity has the authority or capability to oversee, direct, or manage the work or activities of another entity.
-
C.
supervisesMinistry
Indicates that one entity has authoritative oversight and managerial responsibility for the operations and activities of a ministry.
-
D.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
E.
supervisionStatus
Indicates the state or condition of oversight or monitoring that one entity has over another or over a process.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.