Triple
T5952321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunebedden |
E132428
|
entity |
| Predicate | foundArtifacts |
P19329
|
FINISHED |
| Object | pottery |
—
|
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: pottery | Statement: [Hunebedden, foundArtifacts, pottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundArtifacts Context triple: [Hunebedden, foundArtifacts, pottery]
-
A.
discoveredArtifact
Indicates that an entity has found or uncovered a previously unknown or hidden artifact.
-
B.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
C.
originalFindspot
Indicates the location where an object or artifact was first discovered or found in situ.
-
D.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
hasArchaeologicalFeature
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.