Triple
T16119718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joan of Gloucester |
E391100
|
entity |
| Predicate | titleConnection |
P99582
|
FINISHED |
| Object | daughter of a duke |
—
|
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: daughter of a duke | Statement: [Joan of Gloucester, titleConnection, daughter of a duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleConnection Context triple: [Joan of Gloucester, titleConnection, daughter of a duke]
-
A.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
B.
hasConnectionToTitle
chosen
Indicates that one entity is linked or associated with a specific title, role, or designation held or referenced by another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
titleHolderRelationship
Indicates a relationship where one entity holds, possesses, or bears a specific title in connection to another entity or context.
-
E.
titleCombinesWith
Indicates that one title can be merged or used together with another title to form a combined or composite title.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016d527c8190928e73661b18a914 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.