Triple
T15918027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Cerrito archaeological zone |
E386018
|
entity |
| Predicate | startOfMajorOccupation |
P60589
|
FINISHED |
| Object | around 400 CE |
—
|
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: around 400 CE | Statement: [El Cerrito archaeological zone, startOfMajorOccupation, around 400 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfMajorOccupation Context triple: [El Cerrito archaeological zone, startOfMajorOccupation, around 400 CE]
-
A.
earliestMajorOccupation
chosen
Indicates the earliest significant occupation or professional role held by an entity in its life or career timeline.
-
B.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
C.
startedCareerWith
Indicates that an entity began its professional career associated with, employed by, or active for another specified entity.
-
D.
studCareerBegan
Indicates that a student's professional or academic career started at a specified time or institution.
-
E.
occupationBeganAfter
Indicates that one entity’s occupation or job role started at a later time than another specified event or occupation.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.