Triple
T16232423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyrgi |
E394015
|
entity |
| Predicate | PyrgiTabletsImportance |
P122259
|
FINISHED |
| Object | key bilingual text for Etruscan studies |
—
|
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: key bilingual text for Etruscan studies | Statement: [Pyrgi, PyrgiTabletsImportance, key bilingual text for Etruscan studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PyrgiTabletsImportance Context triple: [Pyrgi, PyrgiTabletsImportance, key bilingual text for Etruscan studies]
-
A.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
B.
pyramidExcavator
Indicates a relationship where an entity performs excavation work on or within a pyramid.
-
C.
broughtToEgypt
Indicates that one entity caused another entity to be taken or transported to Egypt.
-
D.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
-
E.
sharesWithPtolemaic
Indicates that something is shared with, or jointly possessed or used by, a Ptolemaic entity.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2b0cc48190853919135d5a172a |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.