Triple
T3895362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Su Nuraxi di Barumini |
E88157
|
entity |
| Predicate | majorExcavationEnd |
P46540
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Su Nuraxi di Barumini, majorExcavationEnd, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationEnd Context triple: [Su Nuraxi di Barumini, majorExcavationEnd, 1950s]
-
A.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
excavationEnd
chosen
Indicates the point in time or event at which an excavation activity is completed or brought to an end.
-
C.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
D.
excavationResumed
Indicates that a previously halted excavation activity has been started again.
-
E.
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).
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.