Triple
T1098342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal President of the Republic |
E24318
|
entity |
| Predicate | uniqueTitleHolderCount |
P24114
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Eternal President of the Republic, uniqueTitleHolderCount, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueTitleHolderCount Context triple: [Eternal President of the Republic, uniqueTitleHolderCount, 1]
-
A.
titleCount
Indicates the number of distinct titles associated with an entity within a given context.
-
B.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
C.
titleNumber
Indicates the numerical designation or sequence number assigned to a title within an ordered set of titles.
-
D.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
E.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
- F. None of above. chosen
Provenance (4 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9bd4eec819094fe09e13b7b07b8 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:43 p.m.