Triple
T2380082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica Aemilia |
E46290
|
entity |
| Predicate | excavatedIn |
P38373
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Basilica Aemilia, excavatedIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavatedIn Context triple: [Basilica Aemilia, excavatedIn, 19th century]
-
A.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
B.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
C.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
D.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
-
E.
excavated
Indicates that one entity has dug out, uncovered, or removed earth or material from another entity, typically to reveal or extract what lies beneath.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7b60c8c819080e4f682e4362a93 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6f4245881909282b3184a288e2a |
completed | March 7, 2026, 6:34 a.m. |
Created at: March 4, 2026, 7:57 p.m.