Triple
T7525372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashupatinath Temple |
E177876
|
entity |
| Predicate | earliestReferenceCentury |
P11826
|
FINISHED |
| Object | 5th century CE (inscriptions) |
—
|
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: 5th century CE (inscriptions) | Statement: [Pashupatinath Temple, earliestReferenceCentury, 5th century CE (inscriptions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestReferenceCentury Context triple: [Pashupatinath Temple, earliestReferenceCentury, 5th century CE (inscriptions)]
-
A.
attestedFromCentury
chosen
Indicates the century from which there is evidence or documentation that something is known to exist or be in use.
-
B.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
C.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
-
D.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
E.
affirmedInCentury
Indicates that a statement, belief, or status was formally confirmed or upheld during a specified century.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c7ac5c8190bbf9befdff791de0 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.