Triple
T36435184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferhotep I |
E897557
|
entity |
| Predicate | nameInModernScholarlyUsage |
P78545
|
FINISHED |
| Object | Neferhotep I |
—
|
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: Neferhotep I | Statement: [Neferhotep I, nameInModernScholarlyUsage, Neferhotep I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInModernScholarlyUsage Context triple: [Neferhotep I, nameInModernScholarlyUsage, Neferhotep I]
-
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.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
-
D.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
E.
isModernName
Indicates that a given name is considered modern or contemporary in usage or origin, as opposed to traditional or historical.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.