Triple
T12546701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karen Baird |
E299986
|
entity |
| Predicate | sharesProfessionalContextWith |
P68404
|
FINISHED |
| Object | Salford City Football Club co-owners |
—
|
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: Salford City Football Club co-owners | Statement: [Karen Baird, sharesProfessionalContextWith, Salford City Football Club co-owners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesProfessionalContextWith Context triple: [Karen Baird, sharesProfessionalContextWith, Salford City Football Club co-owners]
-
A.
sharesProfessionWith
Indicates that two entities have the same profession or occupational role.
-
B.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
C.
sharesContextWith
chosen
Indicates that two entities occur within or are associated with the same situational, semantic, or environmental context.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesInformationWith
Indicates that one entity communicates or provides information to another entity.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.