Triple
T26336370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whittier, Alaska |
E662531
|
entity |
| Predicate | formerMilitaryFacility |
P126626
|
FINISHED |
| Object | Buckner Building |
—
|
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: Buckner Building | Statement: [Whittier, Alaska, formerMilitaryFacility, Buckner Building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMilitaryFacility Context triple: [Whittier, Alaska, formerMilitaryFacility, Buckner Building]
-
A.
formerMilitaryBase
chosen
Indicates that a location was previously used as a military base but no longer serves that function.
-
B.
militaryInstallationType
Indicates the specific category or kind of military installation associated with an entity (e.g., base, fort, airfield, naval station).
-
C.
partOfMilitaryStructure
Indicates that one entity is a component, unit, or subdivision within the organizational hierarchy of a military structure.
-
D.
hostsMilitaryInstallation
Indicates that a location contains or accommodates a military base, facility, or installation operated by armed forces.
-
E.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 26, 2026, 10:36 p.m.