Triple
T22089858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCovey Cove |
E545883
|
entity |
| Predicate | hasCustomTerm |
P146932
|
FINISHED |
| Object | splash hit |
—
|
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: splash hit | Statement: [McCovey Cove, hasCustomTerm, splash hit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomTerm Context triple: [McCovey Cove, hasCustomTerm, splash hit]
-
A.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
B.
hasCanonicalTerm
Indicates that one term in a set is designated as the standard or authoritative form used to represent a concept or entity.
-
C.
hasNumberOfTerms
Indicates the quantity of distinct terms or elements associated with a given entity or expression.
-
D.
hasHigherOrderTerm
Indicates that one entity includes or is associated with a term of higher order (e.g., higher degree, derivative, or complexity) relative to another entity or baseline.
-
E.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e47ba08190a208af72a7cc176f |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:29 p.m.