Triple
T37725301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Falmouth |
E939700
|
entity |
| Predicate | isHereditaryPeerageTitle |
P127258
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Viscount Falmouth, isHereditaryPeerageTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditaryPeerageTitle Context triple: [Viscount Falmouth, isHereditaryPeerageTitle, true]
-
A.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
B.
hereditaryTitleFor
chosen
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
-
C.
hereditaryTitleInheritance
Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
-
D.
hasPeerageTitle
Indicates that an entity holds or is associated with a formal noble or aristocratic title within a peerage system.
-
E.
isFeudalTitle
Indicates that the subject is a title associated with a feudal hierarchy, such as those held within a system of lords, vassals, and land-based obligations.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.