Triple
T26929713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citânia de Briteiros |
E678178
|
entity |
| Predicate | firstExcavation |
P7651
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Citânia de Briteiros, firstExcavation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstExcavation Context triple: [Citânia de Briteiros, firstExcavation, late 19th century]
-
A.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
B.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
C.
laterExcavationsStart
Indicates that the start of one excavation occurs after the start of another excavation.
-
D.
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).
-
E.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 27, 2026, 6:11 a.m.