Triple
T16795235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Wester Wemyss |
E408214
|
entity |
| Predicate | hasFirstHolderOccupation |
P71794
|
FINISHED |
| Object | Royal Navy officer |
—
|
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: Royal Navy officer | Statement: [Baron Wester Wemyss, hasFirstHolderOccupation, Royal Navy officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstHolderOccupation Context triple: [Baron Wester Wemyss, hasFirstHolderOccupation, Royal Navy officer]
-
A.
originalHolderOccupation
chosen
Indicates the occupation or professional role held by the entity that originally possessed or owned another entity.
-
B.
hasFirstHolder
Indicates that an entity is associated with the earliest or original holder (e.g., owner, position-bearer, or title-holder) of something.
-
C.
hasMemberWhoHeldOccupation
Indicates that a group or collective entity includes at least one member who has held a specified occupation.
-
D.
holderIsOccupation
Indicates that the holder entity has the specified occupation or job role.
-
E.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a96d888190a9876c3784bb7f95 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.