Triple
T1065916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean civilization |
E23208
|
entity |
| Predicate | flourishedFrom |
P2559
|
FINISHED |
| Object | c. 3000 BCE |
—
|
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: c. 3000 BCE | Statement: [Andean civilization, flourishedFrom, c. 3000 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flourishedFrom Context triple: [Andean civilization, flourishedFrom, c. 3000 BCE]
-
A.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
B.
flourishedIn
Indicates that an entity experienced its peak activity, success, or prominence during a specified time period or era.
-
C.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
-
D.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
E.
emergedAround
chosen
Indicates that something came into existence or became noticeable at approximately a particular time or period.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.