Triple
T37482393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Romsey |
E931443
|
entity |
| Predicate | isHereditaryUsage |
P188383
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lord Romsey, isHereditaryUsage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHereditaryUsage Context triple: [Lord Romsey, isHereditaryUsage, yes]
-
A.
isHereditaryInPrinciple
Indicates that a characteristic, right, or status is, by its nature or underlying rules, intended to be passed down through inheritance.
-
B.
hasHereditaryBasis
Indicates that a trait, condition, or characteristic is determined or influenced by genetic inheritance passed down through family lines.
-
C.
isHereditaryWithRespectTo
Indicates that a property, trait, or condition is passed down from ancestors to descendants according to genetic or lineage-based inheritance.
-
D.
oftenHereditary
Indicates that the relationship or property typically passes from parents to offspring through genetic inheritance.
-
E.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
- F. None of above. chosen
Provenance (4 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.