Triple
T31069830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Abu Bakar |
E791785
|
entity |
| Predicate | hasRoyalStandard |
P162086
|
FINISHED |
| Object | Royal Standard of the Sultan of Johor |
—
|
NE NERFINISHED |
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: Royal Standard of the Sultan of Johor | Statement: [House of Abu Bakar, hasRoyalStandard, Royal Standard of the Sultan of Johor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalStandard Context triple: [House of Abu Bakar, hasRoyalStandard, Royal Standard of the Sultan of Johor]
-
A.
royalStandard
Indicates that an entity is the official royal flag or emblem used to represent a monarch or royal authority.
-
B.
hasRoyalSymbol
chosen
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
C.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
D.
hasRoyalWarrantFrom
Indicates that one party has been formally granted a royal warrant or official endorsement by a specific royal person or household.
-
E.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 9:01 p.m.