Triple
T18110149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EA 24 |
E433450
|
entity |
| Predicate | inscriptionSide |
P130481
|
FINISHED |
| Object | one side only |
—
|
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: one side only | Statement: [EA 24, inscriptionSide, one side only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionSide Context triple: [EA 24, inscriptionSide, one side only]
-
A.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
B.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
D.
inscriptionID
Indicates a unique identifier that links an entity to a specific inscription or inscribed text.
-
E.
inscriptionSupport
Indicates that one entity serves as the physical surface or material on which another entity (an inscription) is written, carved, or otherwise recorded.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd13cb48190bff06b472e34dd0e |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.