Triple
T13644118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekong region archaeological heritage |
E326058
|
entity |
| Predicate | evidences |
P3650
|
FINISHED |
| Object | early agriculture |
—
|
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: early agriculture | Statement: [Mekong region archaeological heritage, evidences, early agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidences Context triple: [Mekong region archaeological heritage, evidences, early agriculture]
-
A.
providesEvidenceFor
chosen
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
C.
witnesses
Indicates that one entity observes an event, action, or situation involving another entity, typically as a bystander or observer.
-
D.
hasEvidentials
Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
-
E.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5ac2af88190976abe6606994eef |
completed | April 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.