Triple
T6906949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oaxaca Valley |
E159835
|
entity |
| Predicate | prehistoricOccupation |
P22541
|
FINISHED |
| Object | Formative period |
—
|
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: Formative period | Statement: [Oaxaca Valley, prehistoricOccupation, Formative period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prehistoricOccupation Context triple: [Oaxaca Valley, prehistoricOccupation, Formative period]
-
A.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
-
B.
associatedAncientPeoples
Indicates a relationship where certain ancient peoples are historically or culturally linked or connected to a given entity.
-
C.
earliestPermanentSettlement
Indicates that one entity is the location or instance of the first long-term, continuously inhabited settlement associated with another entity.
-
D.
inhabitedSince
chosen
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
E.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d98c3ab08190a1830c45578056ac |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.