Triple
T32716846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King George V National Park |
E836542
|
entity |
| Predicate | successorNameMeaning |
P199728
|
FINISHED |
| Object | “national park” in 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: “national park” in Malay | Statement: [King George V National Park, successorNameMeaning, “national park” in Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameMeaning Context triple: [King George V National Park, successorNameMeaning, “national park” in Malay]
-
A.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
B.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
C.
possibleNameMeaning
Indicates that a given interpretation or semantic meaning is a plausible or potential meaning of a specified name.
-
D.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
E.
successorNameInGreekService
Indicates that the predicate specifies the name of a successor as used or rendered in a Greek-language service or context.
- 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_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: May 1, 2026, 1:11 a.m.