Triple
T30938341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound B |
E788186
|
entity |
| Predicate | excavatedAtTimes |
P38373
|
FINISHED |
| Object | 20th century archaeological investigations |
—
|
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: 20th century archaeological investigations | Statement: [Mound B, excavatedAtTimes, 20th century archaeological investigations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavatedAtTimes Context triple: [Mound B, excavatedAtTimes, 20th century archaeological investigations]
-
A.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
B.
excavatedIn
chosen
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.
excavatedUnder
Indicates that one entity was dug out, uncovered, or removed from beneath another entity during an excavation process.
-
D.
excavatedAfter
Indicates that one excavation event occurred later in time than another excavation event.
-
E.
excavatedSinceCentury
Indicates that an entity has been excavated starting from, or at some point during or after, a specified century.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692e6d7548190a7526bb4be28dc38 |
completed | May 3, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:52 p.m.