Triple
T26681631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westfield-Barnes Regional Airport |
E672627
|
entity |
| Predicate | isJointUse |
P2507
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Westfield-Barnes Regional Airport, isJointUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointUse Context triple: [Westfield-Barnes Regional Airport, isJointUse, yes]
-
A.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
B.
isJointBase
Indicates that two or more components share a common base or foundation point.
-
C.
providesServicesJointlyWith
Indicates that two or more entities collaborate to offer services together as a joint provision rather than independently.
-
D.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
E.
mayBeManagedJointlyWith
Indicates that an entity can be administered, controlled, or overseen together with another entity as part of a shared or coordinated management arrangement.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173a2a208190a8e8bc9513984115 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:20 a.m.