Triple
T31709188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Graham |
E809267
|
entity |
| Predicate | hasFriendInWork |
P177578
|
FINISHED |
| Object | Gerard Jackson |
—
|
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: Gerard Jackson | Statement: [Marcus Graham, hasFriendInWork, Gerard Jackson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFriendInWork Context triple: [Marcus Graham, hasFriendInWork, Gerard Jackson]
-
A.
hasColleagues
Indicates that one entity works alongside another in a professional or organizational context as colleagues.
-
B.
hasFamilyRelationInWork
Indicates that there exists a family relationship between two entities within the context of a specific work (e.g., book, film, or other creative work).
-
C.
hasNotableConnectionToWork
Indicates that there is a significant or noteworthy relationship, influence, or association between an entity and a particular work.
-
D.
hasFriends
chosen
Indicates that an entity is socially connected to one or more other entities in a friendship relationship.
-
E.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 30, 2026, 11:15 p.m.