Triple
T24526170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA Oceania Championship for Men |
E606674
|
entity |
| Predicate | usedAsQualifierSince |
P156612
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [FIBA Oceania Championship for Men, usedAsQualifierSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsQualifierSince Context triple: [FIBA Oceania Championship for Men, usedAsQualifierSince, 20th century]
-
A.
usedToQualify
Indicates that one entity serves as a qualifier or modifier that restricts, specifies, or refines the meaning or scope of another entity.
-
B.
servesAsQualifierFor
Indicates that one entity functions as a qualifier or modifier that refines, restricts, or specifies the meaning or scope of another entity.
-
C.
usesNameSince
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
D.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:25 a.m.