Triple
T28363658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Competitive Strategy: Techniques for Analyzing Industries and Competitors |
E718428
|
entity |
| Predicate | frameworkIntroduced |
P16582
|
FINISHED |
| Object | Five Forces framework |
—
|
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: Five Forces framework | Statement: [Competitive Strategy: Techniques for Analyzing Industries and Competitors, frameworkIntroduced, Five Forces framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkIntroduced Context triple: [Competitive Strategy: Techniques for Analyzing Industries and Competitors, frameworkIntroduced, Five Forces framework]
-
A.
frameworkPresented
chosen
Indicates that a particular framework has been formally introduced or shown to an audience or recipient.
-
B.
frameworkDevelopedBy
Indicates that a software framework was created or developed by a particular person, group, or organization.
-
C.
frameworkName
Indicates that a specific framework is identified by the given name.
-
D.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
E.
frameworkImplementation
Indicates that one entity serves as a concrete implementation or realization of a more abstract framework defined 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 12:53 a.m.