Triple
T684450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca |
E13253
|
entity |
| Predicate | sourceOfAccount |
P409
|
FINISHED |
| Object | narrative recorded by Michael Lok |
—
|
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: narrative recorded by Michael Lok | Statement: [Juan de Fuca, sourceOfAccount, narrative recorded by Michael Lok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfAccount Context triple: [Juan de Fuca, sourceOfAccount, narrative recorded by Michael Lok]
-
A.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
B.
sourceInstitution
Indicates the institution from which something (such as a person, item, or record) originates or is issued.
-
C.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
D.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
E.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0725c708190aa6edfee742ca4e6 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.