Triple
T1501390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pesky's Pole |
E33801
|
entity |
| Predicate | isFeatureOf |
P29386
|
FINISHED |
| Object | Fenway Park right-field line |
—
|
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: Fenway Park right-field line | Statement: [Pesky's Pole, isFeatureOf, Fenway Park right-field line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFeatureOf Context triple: [Pesky's Pole, isFeatureOf, Fenway Park right-field line]
-
A.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
-
B.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
C.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
D.
isModelOf
Indicates that one entity serves as a representation or abstraction that captures the structure or behavior of another entity.
-
E.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90584b8b881908e112c7e59163812 |
completed | March 5, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69a88727ce48819089b482cdc25453d1 |
completed | March 4, 2026, 7:25 p.m. |
| PDg | Predicate description generation | batch_69a90582f2548190bc0a6bdcd6d9d015 |
completed | March 5, 2026, 4:24 a.m. |
Created at: March 4, 2026, 7:24 p.m.