Triple
T29795576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenway South complex |
E756534
|
entity |
| Predicate | hasPracticeFieldType |
P17432
|
FINISHED |
| Object | major league practice fields |
—
|
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: major league practice fields | Statement: [Fenway South complex, hasPracticeFieldType, major league practice fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPracticeFieldType Context triple: [Fenway South complex, hasPracticeFieldType, major league practice fields]
-
A.
hasPracticeFields
chosen
Indicates that an entity possesses or is associated with one or more designated fields or areas used for practice activities.
-
B.
hasPracticeForm
Indicates that an entity is associated with, or takes place in, a particular form or mode of practice.
-
C.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
D.
hasPractices
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
E.
practicedInField
Indicates that an entity has engaged in practical work, training, or professional activity within a specified field or domain.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: April 29, 2026, 5:15 p.m.