Triple
T1973415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regia |
E42850
|
entity |
| Predicate | excavated |
P33350
|
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: [Regia, excavated, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavated Context triple: [Regia, excavated, 19th century]
-
A.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
B.
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).
-
C.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f477988190b0165fc46b1cccfd |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.