Triple
T33687636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JBM–HH |
E863083
|
entity |
| Predicate | componentInstallation |
P96295
|
FINISHED |
| Object | Fort Myer |
—
|
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: Fort Myer | Statement: [JBM–HH, componentInstallation, Fort Myer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentInstallation Context triple: [JBM–HH, componentInstallation, Fort Myer]
-
A.
installedComponent
chosen
Indicates that one entity has been installed as a component or part within another entity or system.
-
B.
installs
Indicates that one entity sets up, places, or integrates another entity so it becomes operational or available for use.
-
C.
installationFeature
Indicates that one entity serves as a feature, component, or functional element of another entity’s installation.
-
D.
installationCommand
Indicates the command or set of commands used to install a particular software, package, or component.
-
E.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:43 a.m.