Triple
T17791374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zipoetes I of Bithynia |
E444168
|
entity |
| Predicate | tookRoyalTitle |
P25963
|
FINISHED |
| Object | c. 297 BC |
—
|
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: c. 297 BC | Statement: [Zipoetes I of Bithynia, tookRoyalTitle, c. 297 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookRoyalTitle Context triple: [Zipoetes I of Bithynia, tookRoyalTitle, c. 297 BC]
-
A.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
B.
tookRegnalName
chosen
Indicates that a person adopted and used a specific official regnal name upon assuming a throne or sovereign rulership.
-
C.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
D.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
E.
royalTitleConfirmed
Indicates that an individual's royal title has been formally validated or officially recognized.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48797408081908c48d98e1525ae87 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.