Triple
T9033883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Air Base |
E216439
|
entity |
| Predicate | wasMajorBaseFor |
P27077
|
FINISHED |
| Object | US tactical air forces in the Pacific |
—
|
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: US tactical air forces in the Pacific | Statement: [Clark Air Base, wasMajorBaseFor, US tactical air forces in the Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorBaseFor Context triple: [Clark Air Base, wasMajorBaseFor, US tactical air forces in the Pacific]
-
A.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
B.
hasMajorBaseAmong
Indicates that one entity has its primary or most significant base of operations located within or among another entity or group.
-
C.
hasMajorUSBase
chosen
Indicates that a location hosts a significant United States military base or installation.
-
D.
isMajorArmOf
Indicates that one entity is a primary or principal branch, division, or extension of another entity.
-
E.
hasMajorBay
Indicates that an entity possesses or is associated with a primary or significant bay.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa248bc8190a55cfc2a5306ab20 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.