Triple
T27777186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Ready For It |
E699225
|
entity |
| Predicate | hasArtistMemberNationality |
P3285
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [Get Ready For It, hasArtistMemberNationality, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistMemberNationality Context triple: [Get Ready For It, hasArtistMemberNationality, British]
-
A.
coArtistNationality
Indicates that two artists who have collaborated share the same nationality.
-
B.
performingArtistNationality
chosen
Indicates the nationality or country of origin of the artist who performs a given work or performance.
-
C.
partOfArtistNationalityContext
Indicates that something functions as a component or aspect of the broader contextual framework surrounding an artist’s nationality.
-
D.
worksWithArtistNationality
Indicates that one entity collaborates or is professionally associated in their work with artists of a specified nationality.
-
E.
hasHonoredArtistNationality
Indicates that an honored artist has a specific nationality associated with their recognition.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:07 p.m.