Triple
T25490123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periplus of the Erythraean Sea |
E638814
|
entity |
| Predicate | describesTradeIn |
P519
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [Periplus of the Erythraean Sea, describesTradeIn, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesTradeIn Context triple: [Periplus of the Erythraean Sea, describesTradeIn, silver]
-
A.
describesTradeIn
Indicates that one entity provides something of value to another entity as part of an exchange or transaction.
-
B.
describesTradeIn
Indicates that one entity provides an item or asset as a trade-in toward acquiring another item or service.
-
C.
describesTradeIn
Indicates a relationship where one party provides an item or asset in exchange for another item, asset, or value as part of a trade-in transaction.
-
D.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
E.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:35 p.m.