Triple
T26650590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Hackett |
E669037
|
entity |
| Predicate | sharesWorkplaceWith |
P184577
|
FINISHED |
| Object | Roy Biggins |
—
|
NE NERFINISHED |
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: Roy Biggins | Statement: [Brian Hackett, sharesWorkplaceWith, Roy Biggins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesWorkplaceWith Context triple: [Brian Hackett, sharesWorkplaceWith, Roy Biggins]
-
A.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
B.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
E.
sharesDepartmentWith
Indicates that two entities work in or are associated with the same department within an organization.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 27, 2026, 2:32 a.m.