Triple
T22950831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-in-C |
E570008
|
entity |
| Predicate | denotesAuthorityLevel |
P4976
|
FINISHED |
| Object | supreme |
—
|
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: supreme | Statement: [C-in-C, denotesAuthorityLevel, supreme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesAuthorityLevel Context triple: [C-in-C, denotesAuthorityLevel, supreme]
-
A.
legalAuthorityLevel
chosen
Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within a given context.
-
B.
authorizationLevel
Indicates the degree or tier of access rights or permissions granted to an entity within a system or context.
-
C.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
D.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
E.
indicatesAuthorityOver
Indicates that one entity holds recognized power, control, or decision-making authority over 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a1b334819097a4e9ea8a54209c |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.