Triple
T36678256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Constables |
E905602
|
entity |
| Predicate | hasSeniorRankTitle |
P59713
|
FINISHED |
| Object | Special Sergeant |
—
|
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: Special Sergeant | Statement: [Special Constables, hasSeniorRankTitle, Special Sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeniorRankTitle Context triple: [Special Constables, hasSeniorRankTitle, Special Sergeant]
-
A.
isSeniorTitle
chosen
Indicates that one title holds a higher or more senior rank or status relative to another title.
-
B.
hasRankOrTitle
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
C.
hasSuperiorGeneralTitle
Indicates that one entity holds a higher-level or more general title or rank in relation to another entity.
-
D.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
E.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
Created at: May 3, 2026, 4:12 p.m.