Triple
T19284660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humphrey Van Weyden |
E482278
|
entity |
| Predicate | forcedIntoRole |
P4672
|
FINISHED |
| Object | cabin boy |
—
|
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: cabin boy | Statement: [Humphrey Van Weyden, forcedIntoRole, cabin boy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedIntoRole Context triple: [Humphrey Van Weyden, forcedIntoRole, cabin boy]
-
A.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
B.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
C.
exportRole
Indicates that an entity functions in a capacity or role specifically related to exporting goods, services, or data.
-
D.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
E.
forcedActionDescribedIn
Indicates that an action was carried out under compulsion or coercion as described in a particular source or description.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc0152d48190b92272d4c7caa708 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.