Triple
T30503263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quedagh Merchant |
E776195
|
entity |
| Predicate | cargoDescription |
P169795
|
FINISHED |
| Object | valuable goods |
—
|
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: valuable goods | Statement: [Quedagh Merchant, cargoDescription, valuable goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoDescription Context triple: [Quedagh Merchant, cargoDescription, valuable goods]
-
A.
cargoContents
Indicates that one entity contains or carries another entity as its cargo.
-
B.
cargoForm
Indicates that one entity serves as the physical or structural form in which another entity’s cargo or contents are contained or transported.
-
C.
cargoAccess
Indicates that an entity has permission or capability to access, enter, or interact with a cargo area or cargo-related contents.
-
D.
cargo
Indicates that one entity is the goods or load being transported, carried, or shipped by another entity.
-
E.
cargoSystem
Indicates a relationship where an entity is part of, managed by, or associated with a cargo-handling or cargo-management system.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687825a248190b587438a58643a32 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:15 p.m.