Triple
T20739040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dot-com bubble |
E509788
|
entity |
| Predicate | notableCompanyType |
P35312
|
FINISHED |
| Object | .com startups |
—
|
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: .com startups | Statement: [dot-com bubble, notableCompanyType, .com startups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompanyType Context triple: [dot-com bubble, notableCompanyType, .com startups]
-
A.
notableBusinessType
chosen
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of business.
-
B.
notableOrganizationType
Indicates that an organization is recognized as being of a particular notable or significant type or category.
-
C.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
D.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
-
E.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20c36708190898b889b6989fc7d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:32 p.m.