Triple
T13096795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry A. Merlo Field |
E310610
|
entity |
| Predicate | onCampusVenueFor |
P36352
|
FINISHED |
| Object | University of Portland soccer programs |
—
|
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: University of Portland soccer programs | Statement: [Harry A. Merlo Field, onCampusVenueFor, University of Portland soccer programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onCampusVenueFor Context triple: [Harry A. Merlo Field, onCampusVenueFor, University of Portland soccer programs]
-
A.
positionOnCampus
Indicates the spatial location or placement of an entity within the boundaries or layout of a campus.
-
B.
hostsCampusOf
Indicates that one entity serves as the physical location or site where another entity’s campus is situated or maintained.
-
C.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
D.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
-
E.
isPartOfCampus
chosen
Indicates that one place, facility, or area is located within and belongs to a larger campus.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9814e88a0819088418c792ce7aa57 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.