Triple
T5641739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigation Act 1660 |
E124281
|
entity |
| Predicate | intendedBeneficiary |
P1806
|
FINISHED |
| Object | English merchants |
—
|
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: English merchants | Statement: [Navigation Act 1660, intendedBeneficiary, English merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBeneficiary Context triple: [Navigation Act 1660, intendedBeneficiary, English merchants]
-
A.
beneficiaryType
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
B.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
C.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
-
D.
primaryBeneficiaries
chosen
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
E.
beneficiaryCountry
Indicates that one country is the recipient or beneficiary of aid, resources, or advantages provided in a given context.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c02286a14481908703ec1741343b76 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.