Triple
T27057021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Field |
E684925
|
entity |
| Predicate | hostInstallationFor |
P78316
|
FINISHED |
| Object | United States Air Force units |
—
|
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: United States Air Force units | Statement: [Pope Field, hostInstallationFor, United States Air Force units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostInstallationFor Context triple: [Pope Field, hostInstallationFor, United States Air Force units]
-
A.
intendedInstallation
Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
-
B.
controlledInstallation
Indicates that an entity has authoritative oversight or management responsibility over the setup, configuration, or deployment of another entity.
-
C.
installationCommand
Indicates the command or set of commands used to install a particular software, package, or component.
-
D.
installationContext
chosen
Indicates the situational or environmental setting in which an installation occurs or is intended to function.
-
E.
installationForm
Indicates the specific method, configuration, or format in which something is installed or set up.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622b425d48190ae5b1490ebee40f2 |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:18 a.m.