Triple
T32716845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King George V National Park |
E836542
|
entity |
| Predicate | languageOfSuccessorName |
P201346
|
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: [King George V National Park, languageOfSuccessorName, Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSuccessorName Context triple: [King George V National Park, languageOfSuccessorName, Malay]
-
A.
successorEnglishName
Indicates that one entity’s English name is the direct successor or replacement of another entity’s English name.
-
B.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
C.
hasOfficialSuccessorName
Indicates that an entity has an officially designated successor identified by a specific name.
-
D.
successorNameInGreekService
Indicates that the predicate specifies the name of a successor as used or rendered in a Greek-language service or context.
-
E.
successorNameForm
Indicates that the object is the name or naming form used for the successor entity that follows the subject in a sequence or lineage.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_69ffecdbe62081909f901e7d4db69d60 |
completed | May 10, 2026, 2:26 a.m. |
Created at: May 1, 2026, 1:11 a.m.