Triple
T36634626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clontarf Rugby Club |
E904424
|
entity |
| Predicate | fieldedTeamType |
P115677
|
FINISHED |
| Object | senior men’s team |
—
|
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: senior men’s team | Statement: [Clontarf Rugby Club, fieldedTeamType, senior men’s team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldedTeamType Context triple: [Clontarf Rugby Club, fieldedTeamType, senior men’s team]
-
A.
fieldedCombinedTeamIn
Indicates that an entity organized and presented a joint or composite team to participate in a specified event or context.
-
B.
fieldedIn
chosen
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
-
C.
fieldingDismissalsType
Indicates the specific manner or category of dismissal attributed to a fielder’s action in a fielding event.
-
D.
fieldingAbility
Indicates the level or quality of an entity’s skill and effectiveness in performing fielding actions in a game or sport.
-
E.
fieldingSideSelection
Indicates which team or side is chosen or designated to field in a game or match.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.