Triple
T32659160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Peterson |
E834944
|
entity |
| Predicate | hasSecondaryStakeholder |
P1553
|
FINISHED |
| Object | instructors |
—
|
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: instructors | Statement: [Mr. Peterson, hasSecondaryStakeholder, instructors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryStakeholder Context triple: [Mr. Peterson, hasSecondaryStakeholder, instructors]
-
A.
hasStakeholder
chosen
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
B.
hasSecondaryPatron
Indicates that an entity has a secondary, non-primary patron that provides additional support, sponsorship, or backing.
-
C.
hasSecondaryCustomerType
Indicates that an entity is associated with an additional, non-primary customer classification or role.
-
D.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
E.
hasSecondarySee
Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 1, 2026, 1:08 a.m.