Triple
T36493399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya coastal trade network |
E899112
|
entity |
| Predicate | transportedGood |
P5941
|
FINISHED |
| Object | obsidian |
—
|
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: obsidian | Statement: [Maya coastal trade network, transportedGood, obsidian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedGood Context triple: [Maya coastal trade network, transportedGood, obsidian]
-
A.
transportedIn
Indicates that one entity is carried or conveyed inside another entity as a means of transport.
-
B.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
C.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
-
D.
materialTransportedFrom
Indicates that a material or substance is moved or carried from a specified source location to another place.
-
E.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:10 p.m.