Triple
T10866645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Link |
E256547
|
entity |
| Predicate | offeredSupportIn |
P9675
|
FINISHED |
| Object | business planning |
—
|
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: business planning | Statement: [Business Link, offeredSupportIn, business planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredSupportIn Context triple: [Business Link, offeredSupportIn, business planning]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
C.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
D.
offeredIn
chosen
Indicates that something is made available or provided within a particular context, setting, or medium.
-
E.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516e15448190aefdba1aa635baea |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.