Triple
T27538874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoshenq C |
E695175
|
entity |
| Predicate | nameInModernScholarship |
P78545
|
FINISHED |
| Object | Shoshenq C |
—
|
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: Shoshenq C | Statement: [Shoshenq C, nameInModernScholarship, Shoshenq C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInModernScholarship Context triple: [Shoshenq C, nameInModernScholarship, Shoshenq C]
-
A.
hasModernHistoriographicalName
chosen
Indicates that an entity is associated with the name or label used for it in modern historiography.
-
B.
scholarlyName
Indicates the formal scientific or academic name assigned to an entity in scholarly or taxonomic contexts.
-
C.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
D.
hasModernScholarlyTerm
Indicates that there exists a contemporary academic or scholarly term that corresponds to or designates the given entity or concept.
-
E.
nameInWesternTradition
Indicates that an entity’s name is expressed following Western naming conventions, typically with the given name preceding the family name.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5c34cc819099bff36545dd5965 |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:30 p.m.