Triple
T19728605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railway Lands |
E473790
|
entity |
| Predicate | hasSportsFunction |
P137104
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Railway Lands, hasSportsFunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsFunction Context triple: [Railway Lands, hasSportsFunction, yes]
-
A.
hasSportsService
Indicates that an entity provides or is associated with a sports-related service.
-
B.
hasSportsBody
Indicates that an entity possesses a body or physique that is characteristic of someone who regularly engages in sports or athletic activities.
-
C.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
D.
hasSportsRole
Indicates that an entity holds or is assigned a specific role or position within a sports context or organization.
-
E.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fa1bc481908a9e7cf4fc52f75c |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.