Triple
T6387988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Passport Control Office |
E143747
|
entity |
| Predicate | coverActivity |
P56248
|
FINISHED |
| Object | passport control |
—
|
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: passport control | Statement: [British Passport Control Office, coverActivity, passport control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverActivity Context triple: [British Passport Control Office, coverActivity, passport control]
-
A.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
B.
coversActionType
chosen
Indicates that one entity’s scope, responsibility, or applicability includes or encompasses a particular type of action.
-
C.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
D.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
E.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686b4f34819088ff07185b34e536 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.