Triple
T18078828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Somerset |
E432629
|
entity |
| Predicate | linkedToIllegitimateLine |
P129724
|
FINISHED |
| Object | Beaufort descendants of John of Gaunt |
—
|
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: Beaufort descendants of John of Gaunt | Statement: [Duke of Somerset, linkedToIllegitimateLine, Beaufort descendants of John of Gaunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToIllegitimateLine Context triple: [Duke of Somerset, linkedToIllegitimateLine, Beaufort descendants of John of Gaunt]
-
A.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
B.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
C.
belongsToLine
Indicates that an entity is a member or component of a particular line or linear grouping.
-
D.
sharesTrunkLineWith
Indicates that two entities are connected to or use the same primary communication or utility trunk line.
-
E.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9f6a85481909894c39c8be98d5d |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:27 a.m.