Triple
T27479388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sligo Rovers F.C. |
E693557
|
entity |
| Predicate | hasHomePitchType |
P38697
|
FINISHED |
| Object | grass |
—
|
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: grass | Statement: [Sligo Rovers F.C., hasHomePitchType, grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomePitchType Context triple: [Sligo Rovers F.C., hasHomePitchType, grass]
-
A.
hasPitchType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
B.
hasHomeTeamType
Indicates that an entity has a specified classification or category for its home team (e.g., type or role of the home team in a competition).
-
C.
hasPitchSurface
Indicates that one entity possesses or is characterized by a particular pitch surface (e.g., a sloped or inclined surface).
-
D.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
E.
usesBaseballStadium
Indicates that an entity regularly occupies or operates within a particular baseball stadium as its primary venue or facility.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 12:58 p.m.