Triple
T25787573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhyiddin |
E649460
|
entity |
| Predicate | bearerCentury |
P89519
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Muhyiddin, bearerCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerCentury Context triple: [Muhyiddin, bearerCentury, 13th century]
-
A.
hasNotableBearerCentury
Indicates that an entity has at least one notable bearer whose period of notability falls within the specified century.
-
B.
ownedUntilCentury
Indicates that an entity possessed or held ownership of another entity up to, but not necessarily beyond, a specified century.
-
C.
ownedInCentury
Indicates that one entity owned another during a specified century.
-
D.
claimedInCentury
Indicates that a claim or assertion was made or recorded during a specified century.
-
E.
associatedWithCenturyOfNameBearer
chosen
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 5:56 a.m.