Triple
T25344614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P. B. Van Trump |
E635510
|
entity |
| Predicate | hasPartnershipOrCollaboration |
P88250
|
FINISHED |
| Object | Hazard Stevens |
—
|
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: Hazard Stevens | Statement: [P. B. Van Trump, hasPartnershipOrCollaboration, Hazard Stevens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnershipOrCollaboration Context triple: [P. B. Van Trump, hasPartnershipOrCollaboration, Hazard Stevens]
-
A.
hasPartnershipRole
Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
-
B.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
-
C.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
-
D.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
E.
hasPartnerInWork
chosen
Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:33 p.m.