Triple
T30218315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFB Goose Bay |
E768268
|
entity |
| Predicate | hasCivilianComponent |
P63390
|
FINISHED |
| Object | Goose Bay Airport |
—
|
NE NERFINISHED |
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: Goose Bay Airport | Statement: [CFB Goose Bay, hasCivilianComponent, Goose Bay Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivilianComponent Context triple: [CFB Goose Bay, hasCivilianComponent, Goose Bay Airport]
-
A.
hasCivilianClass
Indicates that an entity is associated with or belongs to a particular civilian classification or category.
-
B.
isCivilian
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
-
C.
includedCivilianComponent
chosen
Indicates that a military or organizational entity has incorporated a civilian element or participation as part of its structure or operation.
-
D.
hasCivilianIdentity
Indicates that an entity possesses a non-superhero, everyday personal identity used in civilian life.
-
E.
isCivilianBased
Indicates that something is primarily oriented toward, derived from, or operating within a civilian (non-military) context.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 7:34 p.m.