Triple
T28847216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | macellum of Aezani |
E728484
|
entity |
| Predicate | hasTypeOfInscription |
P169889
|
FINISHED |
| Object | economic regulation inscription |
—
|
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: economic regulation inscription | Statement: [macellum of Aezani, hasTypeOfInscription, economic regulation inscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfInscription Context triple: [macellum of Aezani, hasTypeOfInscription, economic regulation inscription]
-
A.
hasTypeOfInscriptions
chosen
Indicates that an entity bears or is associated with a specific kind or category of inscriptions.
-
B.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
C.
mayBeInscribedOn
Indicates that one entity is permitted or suitable to be written, engraved, or otherwise inscribed on another entity.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
hasTypicalInscriptionMethod
Indicates the usual or characteristic method by which inscriptions are applied or created on an object or surface.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 6:42 a.m.