Triple
T99506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English merchants of the Company of Adventurers |
E2008
|
entity |
| Predicate | sought |
P1857
|
FINISHED |
| Object | new trade routes |
—
|
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: new trade routes | Statement: [English merchants of the Company of Adventurers, sought, new trade routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sought Context triple: [English merchants of the Company of Adventurers, sought, new trade routes]
-
A.
remedySought
Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
-
B.
explored
Indicates that an entity has traveled through, examined, or investigated another entity or area, typically to discover or learn more about it.
-
C.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
-
E.
explores
chosen
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.