Triple
T36666899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV44 |
E905289
|
entity |
| Predicate | datingTo |
P52397
|
FINISHED |
| Object | New Kingdom of Egypt |
—
|
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: New Kingdom of Egypt | Statement: [KV44, datingTo, New Kingdom of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datingTo Context triple: [KV44, datingTo, New Kingdom of Egypt]
-
A.
likelyDatingTo
Indicates that something probably originates from or was created in a particular time period or date range.
-
B.
receivesDatingAdviceFrom
Indicates that one person obtains guidance or suggestions about dating from another person.
-
C.
likelyDatingFrom
chosen
Indicates that something is estimated or believed to originate from, or have begun in, a particular time period or date.
-
D.
scientificDating
Indicates that an object or material has been assigned an age or time period using scientific dating methods (e.g., radiocarbon, dendrochronology, or other analytical techniques).
-
E.
usedForDating
Indicates a relationship where one entity is used as a means, tool, or context for engaging in romantic or dating activities with another entity.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c780ecd0819080da2a286bf91257 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.