Triple
T15804626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Anthem of Singapore |
E383177
|
entity |
| Predicate | anthemLanguage |
P120151
|
FINISHED |
| Object | Malay |
—
|
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: Malay | Statement: [National Anthem of Singapore, anthemLanguage, Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anthemLanguage Context triple: [National Anthem of Singapore, anthemLanguage, Malay]
-
A.
anthemType
Indicates the specific category or kind of anthem that characterizes the relationship between the subject and its anthem.
-
B.
anthemComposer
Indicates that one entity is the person who composed the anthem associated with another entity.
-
C.
anthemPerformerCanadian
Indicates that the subject is a Canadian performer who performs or has performed a national anthem.
-
D.
anthemBackedBy
Indicates that an anthem is officially supported, endorsed, or accompanied by a particular backing entity, such as an organization, arrangement, or musical backing.
-
E.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b525b1c08190acffab06d89dbdbe |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e00e48d49c819081afccb02f9cf18b |
completed | April 15, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:48 a.m.