Triple
T1939442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brotherly Leader and Guide of the Revolution |
E41517
|
entity |
| Predicate | notFormalOffice |
P4154
|
FINISHED |
| Object | president |
—
|
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: president | Statement: [Brotherly Leader and Guide of the Revolution, notFormalOffice, president]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notFormalOffice Context triple: [Brotherly Leader and Guide of the Revolution, notFormalOffice, president]
-
A.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
B.
hasInformalStatus
chosen
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
C.
formalityLevel
Indicates the degree of social or stylistic formality characterizing an interaction, expression, or context between entities.
-
D.
officialIn
Indicates that an entity holds an official position, role, or office within a specified organization, institution, or jurisdiction.
-
E.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2ca385c8190ad0e4bafbb9b5e5c |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.