Triple
T23256576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republican Constitution of 1971 |
E581890
|
entity |
| Predicate | definedRole |
P8683
|
FINISHED |
| Object | President as head of state |
—
|
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 as head of state | Statement: [Republican Constitution of 1971, definedRole, President as head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedRole Context triple: [Republican Constitution of 1971, definedRole, President as head of state]
-
A.
definesRole
chosen
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
B.
canonicalRole
Indicates that an entity holds a standard, primary, or officially recognized role within a particular context or system.
-
C.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to another entity.
-
D.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
-
E.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c4905c819099ca21c6529413ac |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.