Triple
T26251190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucking |
E656592
|
entity |
| Predicate | archaeologyExcavatedFrom |
P26977
|
FINISHED |
| Object | gravel pits |
—
|
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: gravel pits | Statement: [Mucking, archaeologyExcavatedFrom, gravel pits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologyExcavatedFrom Context triple: [Mucking, archaeologyExcavatedFrom, gravel pits]
-
A.
excavatedFrom
chosen
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
B.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
-
C.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
D.
excavatedAs
Indicates that one entity has been dug out, uncovered, or removed from its surrounding material or context in the form or role of another specified entity.
-
E.
excavatedFor
Indicates that something has been dug out or uncovered from the ground specifically for the benefit, use, or purpose of another entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dca3cb881908b89f0ace35212fe |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:07 p.m.