Triple
T25618220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Football Club |
E642215
|
entity |
| Predicate | hasAbbrevCommonUsage |
P46512
|
FINISHED |
| Object | RFC |
—
|
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: RFC | Statement: [Richmond Football Club, hasAbbrevCommonUsage, RFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbrevCommonUsage Context triple: [Richmond Football Club, hasAbbrevCommonUsage, RFC]
-
A.
hasCommonAcronymUsage
chosen
Indicates that two terms share the same commonly used acronym in practice.
-
B.
canBeUsedWithAbbreviation
Indicates that one entity (such as a term, phrase, or expression) is suitable to be used together with a particular abbreviation.
-
C.
usesAbbreviationOf
Indicates that one entity employs a shortened or abbreviated form of the name or designation of another entity.
-
D.
isCommonAbbreviation
Indicates that one term is a widely used shortened or abbreviated form of another term.
-
E.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa1e8d948190aab191bfa2226fb8 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:02 p.m.