Triple
T8064868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayala Cove |
E188217
|
entity |
| Predicate | isPrimaryLandingFor |
P80300
|
FINISHED |
| Object | Angel Island State Park visitors |
—
|
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: Angel Island State Park visitors | Statement: [Ayala Cove, isPrimaryLandingFor, Angel Island State Park visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryLandingFor Context triple: [Ayala Cove, isPrimaryLandingFor, Angel Island State Park visitors]
-
A.
hasPrimaryRoute
Indicates that one entity is designated as the main or principal route associated with another entity.
-
B.
landingRequires
Indicates that performing a landing action is contingent upon satisfying a specified requirement or precondition.
-
C.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
D.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
E.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fd07fd08190a3b61cb3369ee6a6 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:26 p.m.