Triple
T15448608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicús culture |
E370088
|
entity |
| Predicate | mainDiscoveryPeriod |
P61044
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Vicús culture, mainDiscoveryPeriod, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDiscoveryPeriod Context triple: [Vicús culture, mainDiscoveryPeriod, 1960s]
-
A.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
-
B.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
C.
mainDiscoverySite
Indicates the primary location where something (such as an object, specimen, or phenomenon) was originally discovered.
-
D.
timeGapBetweenCreationAndDiscovery
Indicates the length of time that passes between when something is created and when it is discovered.
-
E.
discoveryEra
chosen
Indicates the historical period or era during which the entity was discovered or first identified.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef9334c81908541e231b43eb012 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.