Triple
T24584681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferibre |
E608351
|
entity |
| Predicate | correspondsToPersonalName |
P18679
|
FINISHED |
| Object | Psamtik II |
—
|
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: Psamtik II | Statement: [Neferibre, correspondsToPersonalName, Psamtik II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToPersonalName Context triple: [Neferibre, correspondsToPersonalName, Psamtik II]
-
A.
correspondsToSurname
Indicates that one entity is the surname or family name associated with, matching, or representing the other entity.
-
B.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
C.
usesPersonalNamesFrom
Indicates that one entity employs or adopts the system or set of personal names originating from another entity.
-
D.
appliesToPersonBirthName
chosen
Indicates that the referenced value is used as the birth name of the specified person.
-
E.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a98600888190aa631d2c237af60a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.