Triple
T30800021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Luis |
E784337
|
entity |
| Predicate | archaeologyBegan |
P28985
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Mission San Luis, archaeologyBegan, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologyBegan Context triple: [Mission San Luis, archaeologyBegan, 20th century]
-
A.
archaeologyAt
Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
-
B.
archaeologicallyExploredSince
chosen
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
-
C.
archaeologicalHorizon
Indicates a temporal layer or phase in the archaeological record that groups artifacts and features sharing similar characteristics and dating to the same general period.
-
D.
archaeologicalDiscipline
Indicates that one entity is an archaeological field or subfield in which the other entity (such as a person, project, or work) is specialized or involved.
-
E.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:42 p.m.