Triple
T13625778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angaur Airstrip |
E325576
|
entity |
| Predicate | isRemoteFacility |
P90831
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Angaur Airstrip, isRemoteFacility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemoteFacility Context triple: [Angaur Airstrip, isRemoteFacility, true]
-
A.
isPrimaryFacilityFor
Indicates that one facility serves as the main or principal location responsible for supporting or serving a particular entity or operation.
-
B.
isWithinFacility
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
-
C.
appliesToFacility
chosen
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, valid for, or in effect at a particular facility.
-
D.
isRemoteOutpostFor
Indicates that one location functions as a distant, often isolated operational base or support site for another primary location or organization.
-
E.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or place).
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.