Triple
T24321515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Randolph Hearst Memorial Beach |
E612974
|
entity |
| Predicate | hasPierUse |
P155549
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [William Randolph Hearst Memorial Beach, hasPierUse, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPierUse Context triple: [William Randolph Hearst Memorial Beach, hasPierUse, fishing]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
-
C.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
D.
hasNearbyPier
Indicates that one entity is located close to a pier associated with or adjacent to another entity.
-
E.
hasPierLength
Indicates that one entity (typically a pier or similar structure) has a specified length measurement.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ac7fc08190993f707f2f97e7f5 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:51 a.m.