Triple
T11454954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silicon Roundabout |
E271501
|
entity |
| Predicate | gainedProminence |
P24496
|
FINISHED |
| Object | late 2000s |
—
|
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: late 2000s | Statement: [Silicon Roundabout, gainedProminence, late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedProminence Context triple: [Silicon Roundabout, gainedProminence, late 2000s]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
gainedRecognition
Indicates that an entity received acknowledgment, acclaim, or validation from others for its qualities, actions, or achievements.
-
C.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
D.
unitOfProminence
Indicates that one entity specifies the unit or scale in which the prominence or significance of another entity is measured or expressed.
-
E.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.