Triple
T5365187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Churchill |
E103111
|
entity |
| Predicate | memberNotableProfession |
P35550
|
FINISHED |
| Object | soldier |
—
|
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: soldier | Statement: [House of Churchill, memberNotableProfession, soldier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberNotableProfession Context triple: [House of Churchill, memberNotableProfession, soldier]
-
A.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
B.
memberProfession
chosen
Indicates that a member or individual holds or practices a particular profession or occupation.
-
C.
notableOccupationContext
Indicates that the referenced occupation is notable or significant specifically within the given contextual framework or domain.
-
D.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
E.
notableCharacterOccupation
Indicates that a notable character is associated with a specific occupation or professional role.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865eb23481908d32fae4efd86efa |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.