Triple
T30126349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGKB |
E765704
|
entity |
| Predicate | isCivilEnclaveOnFormerMilitaryBase |
P114333
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EGKB, isCivilEnclaveOnFormerMilitaryBase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilEnclaveOnFormerMilitaryBase Context triple: [EGKB, isCivilEnclaveOnFormerMilitaryBase, yes]
-
A.
isCivilEnclave
chosen
Indicates that a location or facility is a civilian enclave situated within or using a military airfield or installation.
-
B.
formerMilitaryBase
Indicates that a location was previously used as a military base but no longer serves that function.
-
C.
hasFormerMilitaryInstallationNearby
Indicates that an entity is located close to a site where a military installation previously existed but is no longer active.
-
D.
isMilitaryInstallation
Indicates that a location functions as a military facility or base used for defense, training, operations, or related armed forces activities.
-
E.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67deffb10819082e0bd841b65883e |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:14 p.m.