Triple
T3805974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of the Kings |
E93006
|
entity |
| Predicate | discoveredByWesternersCentury |
P51861
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Valley of the Kings, discoveredByWesternersCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByWesternersCentury Context triple: [Valley of the Kings, discoveredByWesternersCentury, 18th century]
-
A.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
B.
rediscoveredInCentury
Indicates that something previously known but lost or forgotten was found or recognized again during a specified century.
-
C.
rediscoveredIn
Indicates that something previously known but lost or forgotten was found or identified again at a particular time or place.
-
D.
revealedInCentury
Indicates that something became known, disclosed, or publicly revealed during a specified century.
-
E.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
- F. None of above. chosen
Provenance (4 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:16 p.m.