Triple
T21551806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Royals FC |
E531779
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | URFC |
—
|
NE NERFINISHED |
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: URFC | Statement: [Utah Royals FC, shortName, URFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: URFC Context triple: [Utah Royals FC, shortName, URFC]
-
A.
URFC
chosen
URFC is the commonly used abbreviation for Utah Royals FC, a professional women's soccer club based in Utah that has competed in the National Women's Soccer League.
-
B.
UrFU
UrFU is a major Russian public research university located in Yekaterinburg, known for its strong engineering, technical, and applied science programs.
-
C.
RFU
RFU is the commonly used abbreviation for the Russian Football Union, the governing body of football in Russia.
-
D.
RFU
RFU is a health sciences university known for training professionals in medicine, pharmacy, podiatry, and related biomedical fields.
-
E.
LRFC
LRFC is the commonly used abbreviation for Lisburn Rangers Football Club, a Northern Irish association football team.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:29 p.m.