Triple
T32062181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Licensing |
E818773
|
entity |
| Predicate | servedStakeholder |
P1553
|
FINISHED |
| Object | patent holders |
—
|
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: patent holders | Statement: [Via Licensing, servedStakeholder, patent holders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedStakeholder Context triple: [Via Licensing, servedStakeholder, patent holders]
-
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.
primaryStakeholder
Indicates that an entity is the main party with the greatest interest, responsibility, or influence in relation to another entity, project, or decision.
-
C.
stakeholderIndustry
Indicates the industry or sector in which a stakeholder operates or is primarily involved.
-
D.
stakeholderSubsidiary
Indicates that one entity is a subsidiary company or organization of another stakeholder entity.
-
E.
engagesStakeholdersFrom
Indicates that an entity actively involves or consults stakeholders originating from a specified source or 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 12:22 a.m.