Triple
T8355481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Cochrane |
E196670
|
entity |
| Predicate | hasIrishFamilyConnections |
P13742
|
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: [Thomas Cochrane, hasIrishFamilyConnections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIrishFamilyConnections Context triple: [Thomas Cochrane, hasIrishFamilyConnections, true]
-
A.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
-
B.
hasCelticName
Indicates that an entity possesses a name that is of Celtic origin or in a Celtic language.
-
C.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
D.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
-
E.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8048edb88190a1980ad74818b898 |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.