Triple
T30647485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Weymouth |
E780162
|
entity |
| Predicate | formerFacilityNearby |
P198696
|
FINISHED |
| Object | Naval Air Station South Weymouth |
—
|
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: Naval Air Station South Weymouth | Statement: [South Weymouth, formerFacilityNearby, Naval Air Station South Weymouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFacilityNearby Context triple: [South Weymouth, formerFacilityNearby, Naval Air Station South Weymouth]
-
A.
operatedFacilityNear
Indicates that an entity operated a facility located in close geographic proximity to another specified entity or place.
-
B.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
C.
nearbyFacilityType
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
D.
formerPrimaryFunctionOfNearbyFacility
Indicates that the referenced role or use was previously the main function of a facility located nearby.
-
E.
formerHomeFacility
Indicates that an entity was previously housed, based, or operated in a particular facility but no longer is.
- F. None of above. chosen
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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: April 29, 2026, 8:29 p.m.