Triple
T4614331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterActiveCorp |
E100829
|
entity |
| Predicate | hasBusinessStrategy |
P20310
|
FINISHED |
| Object | acquisition and incubation of online brands |
—
|
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: acquisition and incubation of online brands | Statement: [InterActiveCorp, hasBusinessStrategy, acquisition and incubation of online brands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessStrategy Context triple: [InterActiveCorp, hasBusinessStrategy, acquisition and incubation of online brands]
-
A.
businessStrategy
chosen
Indicates the overarching plan or approach an entity adopts to achieve its business goals, compete in its market, and allocate resources.
-
B.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
C.
hasBusinessNode
Indicates that an entity is associated with, linked to, or represented by a specific business-related node within a business structure or network.
-
D.
hasStrategicFunction
Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
-
E.
hasBusinessRoute
Indicates that there exists an established commercial or service route connecting two business-related entities.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59c2678c8190ab8f9420e866521d |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.