Triple
T24584695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferibre |
E608351
|
entity |
| Predicate | usedInChronologicalRecords |
P41120
|
FINISHED |
| Object | king lists |
—
|
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: king lists | Statement: [Neferibre, usedInChronologicalRecords, king lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChronologicalRecords Context triple: [Neferibre, usedInChronologicalRecords, king lists]
-
A.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
B.
chronologicallyInvolvedIn
Indicates that an entity participates in or is associated with an event, process, or activity during a specific time period in a chronological sequence.
-
C.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
D.
chronologyIncludes
Indicates that a broader chronological sequence or timeline encompasses a specific time span, event, or period as part of it.
-
E.
chronicledBy
chosen
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
- 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.