Triple
T24454183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemib |
E616631
|
entity |
| Predicate | holderCapital |
P44004
|
FINISHED |
| Object | Sais |
—
|
NE NERFINISHED |
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: Sais | Statement: [Sekhemib, holderCapital, Sais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderCapital Context triple: [Sekhemib, holderCapital, Sais]
-
A.
authorizedCapital
Indicates the legally approved maximum amount of share capital that a company is permitted to issue under its corporate charter or governing documents.
-
B.
hasCoCapital
Indicates that two or more cities share the status and functions of being capital cities of the same political or administrative entity.
-
C.
hasAssociatedCapital
chosen
Indicates that an entity is linked to a specific capital city that serves as its primary administrative or political center.
-
D.
roleOfHolders
Indicates that certain entities serve as holders or bearers of a specified role, function, or position in relation to something else.
-
E.
majorShareholderOf
Indicates that one entity owns a controlling or significantly large portion of another entity’s shares or equity.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c4f1d881909d9119fec74afe53 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.