Triple
T35511198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayrest |
E1026288
|
entity |
| Predicate | tradeSpecialty |
P67985
|
FINISHED |
| Object | maritime trade |
—
|
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: maritime trade | Statement: [Wayrest, tradeSpecialty, maritime trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeSpecialty Context triple: [Wayrest, tradeSpecialty, maritime trade]
-
A.
marketSpecialization
Indicates a relationship where an entity focuses its activities, products, or services on serving a specific segment or niche of a broader market.
-
B.
craftSpecialty
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
C.
shopSpecialty
Indicates that a shop primarily focuses on or is specially known for offering a particular type of product or service.
-
D.
tradeFocus
chosen
Indicates a primary emphasis on or specialization in a particular type of trade, transaction, or commercial activity within the relationship or context.
-
E.
tradeHubWith
Indicates that one entity functions as a central location or node for trading activities in connection with 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.