Triple
T24406880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRE |
E615333
|
entity |
| Predicate | codeSystemScope |
P19702
|
FINISHED |
| Object | international rugby union |
—
|
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: international rugby union | Statement: [IRE, codeSystemScope, international rugby union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSystemScope Context triple: [IRE, codeSystemScope, international rugby union]
-
A.
standardCodeSystem
Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
-
B.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
C.
standardizationScope
chosen
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
D.
administrativeCodeSystem
Indicates that there is a system or scheme used to assign and manage administrative codes for organizing or identifying entities or records.
-
E.
codenameScope
Indicates that a particular codename is valid, applicable, or recognized only within a specified scope or contextual 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957e8d5c8190bfed93aa308eb523 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.