Triple
T5540769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gobustan Rock Art Cultural Landscape |
E145280
|
entity |
| Predicate | RomanInscriptionDate |
P33352
|
FINISHED |
| Object | 1st century AD |
—
|
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: 1st century AD | Statement: [Gobustan Rock Art Cultural Landscape, RomanInscriptionDate, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanInscriptionDate Context triple: [Gobustan Rock Art Cultural Landscape, RomanInscriptionDate, 1st century AD]
-
A.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
B.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
C.
positionInRomanCalendar
Indicates the ordinal placement or rank that something occupies within the sequence of months or days in the Roman calendar.
-
D.
inscribedOn
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
-
E.
inscriptionDating
chosen
Indicates the temporal period or specific date to which an inscription is assigned or attributed.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.