Triple
T25771131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPSM |
E649022
|
entity |
| Predicate | locatedOnFormerBase |
P129411
|
FINISHED |
| Object | Pease Air Force Base |
E624667
|
NE 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: Pease Air Force Base | Statement: [KPSM, locatedOnFormerBase, Pease Air Force Base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnFormerBase Context triple: [KPSM, locatedOnFormerBase, Pease Air Force Base]
-
A.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
-
B.
locatedNearFormer
Indicates that one entity is situated close to another entity that previously occupied a nearby or the same location.
-
C.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
D.
locatedAtFormerAirport
chosen
Indicates that an entity is situated on the site or grounds of an airport that is no longer in operation.
-
E.
locatedWithinFormer
Indicates that one entity is or was geographically contained within the boundaries of another entity that no longer exists in its former administrative or territorial form.
- F. None of above.
Provenance (4 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a164151f6348190a83d4f06ed04ba38 |
completed | May 27, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 22, 2026, 5:29 a.m.