Triple
T15457383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardiff Singer of the World competition |
E371805
|
entity |
| Predicate | hasParticipantNationalityRange |
P118887
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Cardiff Singer of the World competition, hasParticipantNationalityRange, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantNationalityRange Context triple: [Cardiff Singer of the World competition, hasParticipantNationalityRange, global]
-
A.
hasParticipantNationality
Indicates that a participant in an event, activity, or relation has a specific nationality.
-
B.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
-
C.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
-
D.
basedOnNationality
Indicates a relationship where something is determined, derived, or decided according to a person’s nationality.
-
E.
includedNationality
Indicates that one entity’s set of nationalities contains or encompasses the nationality of another entity.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.