Triple
T33858405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yang di-Pertuan Muda of Terengganu |
E867851
|
entity |
| Predicate | hasHistoricalType |
P161624
|
FINISHED |
| Object | feudal title |
—
|
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: feudal title | Statement: [Yang di-Pertuan Muda of Terengganu, hasHistoricalType, feudal title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalType Context triple: [Yang di-Pertuan Muda of Terengganu, hasHistoricalType, feudal title]
-
A.
hasHistoricType
chosen
Indicates that an entity is associated with a specific historical classification, category, or type it held in the past.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
D.
hasHistoricResourceType
Indicates that an entity is associated with a particular category or type of historic resource.
-
E.
hasHistoricEventType
Indicates that a historic event is associated with a specific category or type of historical occurrence.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 1, 2026, 1:47 a.m.