Triple
T23806813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Police Air Service |
E589730
|
entity |
| Predicate | hasCallsignPrefix |
P94340
|
FINISHED |
| Object | Police |
—
|
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: Police | Statement: [National Police Air Service, hasCallsignPrefix, Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallsignPrefix Context triple: [National Police Air Service, hasCallsignPrefix, Police]
-
A.
hasCallSignPrefix
chosen
Indicates that an entity’s call sign begins with a specified prefix.
-
B.
hasCallsignPrefixRole
Indicates that an entity has a specific role associated with a given callsign prefix.
-
C.
hasCallSignOrigin
Indicates that an entity’s call sign originates from, or is derived based on, a particular source, place, or context.
-
D.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
-
E.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c752ff6481908cfc20d4f178d526 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.