Triple
T10120074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Commander of the Order of the Defender of the Realm |
E223261
|
entity |
| Predicate | hasOrderMottoLanguage |
P17012
|
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: [Grand Commander of the Order of the Defender of the Realm, hasOrderMottoLanguage, Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderMottoLanguage Context triple: [Grand Commander of the Order of the Defender of the Realm, hasOrderMottoLanguage, Malay]
-
A.
mottoOriginalLanguage
chosen
Indicates the language in which a motto was originally formulated or expressed.
-
B.
hasMottoLanguageContext
Indicates that a motto is associated with a specific language context in which it is expressed or interpreted.
-
C.
orderMottoPromoted
Indicates that a motto associated with an order has been elevated or given increased prominence or status.
-
D.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
E.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2659cdc8190b3ba91426bda55ec |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.